From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [patch RFC] Re: Notes on a frame_unwind_address_in_block problem
Date: Wed, 03 Jan 2007 22:23:00 -0000 [thread overview]
Message-ID: <200701032223.l03MN8u0001386@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070103220223.GK17935@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 3 Jan 2007 17:02:24 -0500)
> Date: Wed, 3 Jan 2007 17:02:24 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> On Wed, Jan 03, 2007 at 10:58:25PM +0100, Mark Kettenis wrote:
> > Heh, well, if you do the mechanical frame_unwind_address_in_block()
> > changes I'll do frame_func_unwind().
> >
> > After that we can actually worry about about fixing things.
> >
> > Deal?
>
> Absolutely. If you can hand me a patch which adds NORMAL_FRAME to
> every call to frame_func_unwind, I'll do all the rest. I'm pretty
> sure all of the existing call sites are NORMAL_FRAME; there won't be a
> SIGTRAMP_FRAME one until we split out two this_id functions for dwarf2.
>
> I've got frame_unwind_address_in_block done locally.
Hmm, well, you need to commit that one first, because the
frame_func_unwind() change will depend on it.
But perhaps we should give people a few days to comment...
Mark
next prev parent reply other threads:[~2007-01-03 22:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060706222157.GA1377@nevyn.them.org>
[not found] ` <200607132020.k6DKKCSB023812@elgar.sibelius.xs4all.nl>
[not found] ` <20060718183910.GB17864@nevyn.them.org>
2007-01-01 19:19 ` Daniel Jacobowitz
2007-01-01 19:54 ` Mark Kettenis
2007-01-01 20:02 ` Daniel Jacobowitz
2007-01-01 20:27 ` Mark Kettenis
2007-01-01 20:35 ` Daniel Jacobowitz
2007-01-02 0:51 ` Daniel Jacobowitz
2007-01-02 19:16 ` Mark Kettenis
2007-01-02 19:18 ` Daniel Jacobowitz
2007-01-02 19:20 ` Daniel Jacobowitz
2007-01-02 21:32 ` Mark Kettenis
2007-01-03 11:37 ` Mark Kettenis
2007-01-03 14:43 ` Daniel Jacobowitz
2007-01-03 16:13 ` Daniel Jacobowitz
2007-01-03 20:28 ` Mark Kettenis
2007-01-03 20:30 ` Daniel Jacobowitz
2007-01-03 21:58 ` Mark Kettenis
2007-01-03 22:02 ` Daniel Jacobowitz
2007-01-03 22:23 ` Mark Kettenis [this message]
2007-01-03 22:29 ` Daniel Jacobowitz
2007-02-20 12:39 ` Daniel Jacobowitz
2007-02-20 15:31 ` Daniel Jacobowitz
2007-02-20 16:20 ` Daniel Jacobowitz
2007-02-22 21:28 ` Mark Kettenis
2007-02-22 21:32 ` Daniel Jacobowitz
2007-02-27 20:18 ` 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=200701032223.l03MN8u0001386@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@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