From: Mark Kettenis <kettenis@chello.nl>
To: eliz@is.elta.co.il
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Convert i386 target to generic dummy frames
Date: Thu, 04 Jul 2002 06:16:00 -0000 [thread overview]
Message-ID: <200207041124.g64BOI300563@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020704130733.1495A-100000@is> (message from Eli Zaretskii on Thu, 4 Jul 2002 13:08:06 +0300 (IDT))
Date: Thu, 4 Jul 2002 13:08:06 +0300 (IDT)
From: Eli Zaretskii <eliz@is.elta.co.il>
On Thu, 4 Jul 2002, Mark Kettenis wrote:
> This patch converts the i386 target to use generic dummy frames.
> Since this is supposed to be a prerequisit for using the DWARF2 frame
> unwinding stuff, I'll try to figure out how I can use that stuff on
> the i386.
Does this change affect the non-DWARF2 targets in any way?
It shouldn't. The generic dummy frame change influences the way
functions are called from within GDB. We used to execute a bit of
code on the stack, but now GDB directly calls the function and makes
it return to the original entry point of your program where it places
a breakpoint. I noticed some fall out with respect to signal
handlers on FreeBSD and Linux but that should be fixed now. However
there is a change in the way GDB handles these function calls, so
there might be some other bugs that'll surface now.
Once I start messing with the DWARF2 frame stuff, I'll make sure that
when the necessary information isn't present, we fall back on the old
code. Perhaps I'll even add a command to let the user choose.
Mark
next prev parent reply other threads:[~2002-07-04 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 1:18 Mark Kettenis
2002-07-04 4:24 ` Eli Zaretskii
2002-07-04 6:16 ` Mark Kettenis [this message]
2002-07-08 11:08 ` Andrew Cagney
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=200207041124.g64BOI300563@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.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