From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com, fnf@ninemoons.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] - Accept optional printed address at function breakpoints
Date: Mon, 08 Dec 2003 16:53:00 -0000 [thread overview]
Message-ID: <20031208165233.555934B412@berman.michael-chastain.com> (raw)
drow> This is a debug info bug. Your patch is not correct; when you say
drow> "break LINE" or "break FUNCTION" and there is debug info, it's GDB's
drow> established behavior to stop at the beginning of a line. By not
drow> allowing the address we verify that GDB is stopping at the beginning of
drow> a line as expected.
That's right. It's a subtle way of testing that the line number
information is correct. If gdb prints a machine address in addition
to a line number, then either gcc has a bug in debug info output,
or gdb has a bug in debug info input.
Michael C
next reply other threads:[~2003-12-08 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 16:53 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 18:02 Michael Elizabeth Chastain
2003-12-08 16:25 Fred Fish
2003-12-08 16:48 ` Daniel Jacobowitz
2003-12-08 17:51 ` Fred Fish
2003-12-09 4:39 ` 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=20031208165233.555934B412@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@mvista.com \
--cc=fnf@ninemoons.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