From: Daniel Jacobowitz <drow@false.org>
To: Andrew Haley <aph@redhat.com>
Cc: gcc@gcc.gnu.org, gdb-discuss@gnu.org, gdb@sourceware.org
Subject: Re: x86 Q: why aren't the SSE intrinsics always_inline?
Date: Tue, 14 Jun 2005 14:56:00 -0000 [thread overview]
Message-ID: <20050614145552.GA3952@nevyn.them.org> (raw)
In-Reply-To: <17070.41423.645043.983123@zapata.pink>
[Redirecting off the misnamed gdb-discuss list; please use
gdb@sourceware instead.]
On Tue, Jun 14, 2005 at 10:22:23AM +0100, Andrew Haley wrote:
> You have the same problem with Java -- you're stepping through a Java
> program, and all of a sudden you're inside the memory allocator. What
> we _really_ need is some way to tell gdb "I'm debugging my own
> program, not the library" or somesuch. Or, and this is less
> desirable, some way to persuade gcc not to output debug info inside
> some inlined functions, although I can't image how a priori you'd
> decide which ones.
It'd be better to handle this in gdb than in gcc, sure. There's two
parts: better support for inline functions, which is already on the gdb
roadmap, and then some way of selecting which ones to ignore. And for
that latter, I have no idea how it should look...
--
Daniel Jacobowitz
CodeSourcery, LLC
next parent reply other threads:[~2005-06-14 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96B69900-04F0-406A-9B53-F74B6D2B8071@apple.com>
[not found] ` <17070.41423.645043.983123@zapata.pink>
2005-06-14 14:56 ` Daniel Jacobowitz [this message]
2005-06-15 1:12 ` [Gdb-discuss] " Fred Fish
2005-06-15 1:17 ` Daniel Jacobowitz
2005-06-15 1:48 ` 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=20050614145552.GA3952@nevyn.them.org \
--to=drow@false.org \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-discuss@gnu.org \
--cc=gdb@sourceware.org \
/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