On Mon, 2013-01-07 at 20:30 +0000, Richard Sandiford wrote: > "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 > > 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
No, I don't know why I get the execution failure. I dug around a bit but could not figure out what or where the problem was coming from. I assume the executable is accessing a bad address or an uninitialized bit of memory somewhere but I could not figure out where. The actual executable code is the same with or without the debug information. I don't even know if this is a bug in GCC or in the GNU simulator. My inability to figure out where the problem was occurring is the main reason I started wondering why I even cared about stabs. Steve Ellcey sell...@mips.com
