From: Steve Ellcey <sellcey@mips.com>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, mips, stabs] Do any MIPS targets use stabs?
Date: Mon, 07 Jan 2013 20:41:00 -0000 [thread overview]
Message-ID: <1357591286.1703.4.camel@ubuntu-sellcey> (raw)
In-Reply-To: <87ip784tyl.fsf@talisman.default>
On Mon, 2013-01-07 at 20:30 +0000, Richard Sandiford wrote:
> "Steve Ellcey " <sellcey@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
sellcey@mips.com
prev parent reply other threads:[~2013-01-07 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 18:27 Steve Ellcey
2013-01-07 20:30 ` Richard Sandiford
2013-01-07 20:38 ` Richard Sandiford
2013-01-07 20:54 ` Steve Ellcey
2013-01-08 16:30 ` Steve Ellcey
2013-01-07 20:41 ` Steve Ellcey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1357591286.1703.4.camel@ubuntu-sellcey \
--to=sellcey@mips.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).