From: Michael Elizabeth Chastain <mec@shout.net>
To: fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Gdb line table implementation tweak
Date: Wed, 27 Feb 2002 16:45:00 -0000 [thread overview]
Message-ID: <200202280045.g1S0j6E19785@duracef.shout.net> (raw)
I'm getting similar failures on:
[target=native host=i686-pc-linux-gnu%rh-7.2 gdb=HEAD%2002-02-26
gcc=2.95.3 glibc=vendor goption=-g-stabs+]
I put up a gdb.log and gdb.sum file on:
ftp://ftp.shout.net/pub/users/mec/step-bug/gdb.sum
ftp://ftp.shout.net/pub/users/mec/step-bug/gdb.log
A good example of the bad behavior is:
gdb.base/step-test: large struct by value
gdb tries to step into a function but instead it steps somewhere else.
For me, the bug is specific to gcc 2.95.3 and stabs debugging format.
Michael C
next reply other threads:[~2002-02-28 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 16:45 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-23 13:52 Michael Elizabeth Chastain
2002-02-12 16:28 Fred Fish
2002-02-13 7:10 ` Daniel Jacobowitz
2002-02-21 12:50 ` Jim Blandy
2002-02-23 13:37 ` Mark Kettenis
2002-02-27 13:43 ` Jim Blandy
2002-02-27 15:24 ` Fred Fish
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=200202280045.g1S0j6E19785@duracef.shout.net \
--to=mec@shout.net \
--cc=fnf@redhat.com \
--cc=gdb-patches@sources.redhat.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