"Steve Ellcey " <sell...@mips.com> writes: > While testing all the variations of my mips-mti-elf target I found that > a number of debug tests like gcc.dg/debug/trivial.c fail when compiled > using a stabs debug flag (-gstabs3 for example) and -mips16. While running > the GNU simulator I get: > > mips-core: 1 byte read to unmapped address 0xffffe820 at 0xffffffff80020278 > program stopped with signal 10 (User defined signal 1). > FAIL: gcc.dg/debug/trivial.c -gstabs3 -O execution test > > Since I don't actually care about STABS I was looking at undefining > DBX_DEBUGGING_INFO in mips-mti-elf.h and mips-mti-linux.h which makes > the failures a moot point for me since I would no longer run the tests > with any -stabs flags. > > But I was wondering, are there any MIPS targets that do use stabs? If not > maybe we should just remove the define of DBX_DEBUGGING_INFO from mips.h > instead of undefing it just for my targets. Opinions?
Do you know why selecting stabs causes an execution failure? That shouldn't happen regardless of whether the debug info itself is good. I don't mind removing stabs from all MIPS targets, but I'd like to understand why we get the execution failure first. Richard
