From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: i386-linux signal backtraces broken
Date: Thu, 10 Oct 2002 12:11:00 -0000 [thread overview]
Message-ID: <20021010191145.GA19287@nevyn.them.org> (raw)
In-Reply-To: <1021010190606.ZM11731@localhost.localdomain>
On Thu, Oct 10, 2002 at 12:06:06PM -0700, Kevin Buettner wrote:
> On Oct 10, 2:47pm, Daniel Jacobowitz wrote:
>
> > We have two choices, that I see:
> > - Call the code inspection functions always
> > - Call the code inspection functions if the name is sigaction, taking
> > advantage of the glibc implementation detail that sigaction is the
> > only exported name for this function that I can see, and they are
> > implemented right after it in the same file.
> >
> > Option (A) is a performance hit. Option (B) is, well, a little fragile.
> >
> > Thoughts?
>
> It sounds to me like option (A) is the way to go. How bad is the
> performance hit?
Hard to say, since I don't have any way to test GDB's reaction speed...
it's going to mean at least one more read from target memory per frame
in a backtrace, for instance.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-10 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 11:46 Daniel Jacobowitz
2002-10-10 12:06 ` Kevin Buettner
2002-10-10 12:11 ` Daniel Jacobowitz [this message]
2002-10-12 10:50 ` Mark Kettenis
2002-10-12 10:55 ` Daniel Jacobowitz
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=20021010191145.GA19287@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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