From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jimb@redhat.com
Cc: gdb@sourceware.org
Subject: Re: Why do we have two ways of finding sniffers?
Date: Thu, 20 Oct 2005 08:46:00 -0000 [thread overview]
Message-ID: <200510200846.j9K8k9ou011894@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <vt2slux2gb5.fsf@theseus.home.> (message from Jim Blandy on Wed, 19 Oct 2005 17:16:46 -0700)
> From: Jim Blandy <jimb@redhat.com>
> Date: Wed, 19 Oct 2005 17:16:46 -0700
>
> I don't understand why we need both alternatives. Shouldn't it be
> sufficient to simply have each entry in the list point to a function
> that expects the next frame's frame_info and a prologue cache, and
> returns a 'struct frame_unwind *' or zero?
I don't think there is a *technical* reason why we need both
alternatives. It's more a matter that we had (and still have to some
extent) a pretty long list of basically unmainted targets. So
converting frame_unwind_append_sniffer() into
frame_unwind_append_unwinder() is difficult to accomplish. But you
should really answer Andrew about this since he wrote that code.
Mark
next prev parent reply other threads:[~2005-10-20 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 0:18 Jim Blandy
2005-10-20 0:25 ` Jim Blandy
2005-10-20 8:46 ` Mark Kettenis [this message]
2005-10-22 1:20 ` Jim Blandy
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=200510200846.j9K8k9ou011894@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.org \
--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