From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: GDB does not show variables in inlined function
Date: Fri, 09 Jan 2004 00:15:00 -0000 [thread overview]
Message-ID: <20040109001521.GA20426@nevyn.them.org> (raw)
In-Reply-To: <vt21xqagf31.fsf@zenia.home>
On Thu, Jan 08, 2004 at 07:06:58PM -0500, Jim Blandy wrote:
>
> I like the patch.
>
> Will the 'breako2' tests in gdb.base/break.exp exercise this?
No, I don't think so. I've been sitting on it until I have time to
exercise it on both a compiler which produces inadequate debug info
(all current GCCs) and one which doesn't (like the hammer or rtlopt
branches, I think).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-01-09 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 14:49 Josef Zlomek
2004-01-06 15:02 ` Daniel Jacobowitz
2004-01-06 15:27 ` Josef Zlomek
2004-01-06 16:23 ` Daniel Jacobowitz
2004-01-06 16:33 ` Josef Zlomek
2004-01-06 16:36 ` Daniel Jacobowitz
2004-01-09 0:13 ` Jim Blandy
2004-01-09 0:15 ` Daniel Jacobowitz [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=20040109001521.GA20426@nevyn.them.org \
--to=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@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