From: John Wehle <john@feith.com>
To: gdb-patches@cygnus.com
Cc: shebs@cygnus.com
Subject: Re: GDB 4.17 Patch for stack aligned i386 code
Date: Wed, 24 Feb 1999 19:41:00 -0000 [thread overview]
Message-ID: <199902250335.WAA27443@jwlab.FEITH.COM> (raw)
Message-ID: <19990224194100.L-x5hnO_rJ4GXQeanyp9mWoc5r9ANj3mUq1wAwZijHM@z> (raw)
Just curious what the status is of this patch. Anything I need
to do at this point?
Wed Jan 20 22:14:03 EST 1999 John Wehle (john@feith.com)
* tm-i386.h (FRAME_CHAIN): Call i386_frame_chain for
signal handler callers.
(EXTRA_FRAME_INFO): Define stack_mask.
(FRAME_ARGS_ADDRESS, FRAME_LOCALS_ADDRESS): Use it.
* i386-tdep.c (i386_get_frame_setup): Set it.
(i386_frame_find_saved_regs): Use it.
(i386_init_extra_frame_info): Initialize it.
(i386_frame_find_saved_regs): Don't accidently zero
fi->fsr.regs[FP_REGNUM].
(i386_sigcontext_addr): New function.
(i386v4_sigtramp_saved_pc): Use it.
(i386_analyze_prologue): Use it.
(i386_analyze_prologue): Handle dummy frames.
(i386_analyze_prologue): If the start of a function can't
be located than assume the frame is in the frame pointer.
(i386_frame_chain): If the caller's prologue can't be
analyze then return the current frame as the frame.
(i386_frame_chain): Check the current frame for FP_REGNUM.
(i386_frame_chain): Handle chaining back from a signal
handler caller to a function which uses the stack pointer
for the frame pointer.
(i386_frame_chain): Include the stack space occupied by
FP_REGNUM when caculating the caller's frame.
(i386_pop_frame): Don't bother explicitly restoring PC_REGNUM,
it is restored by the for loop.
* tm-i386bsd.h (SIGCONTEXT_FP_OFFSET,
SIGCONTEXT_SP_OFFSET): Define.
* tm-i386sol2.h: Likewise.
* tm-i386v4.h: Likewise.
-- John
-------------------------------------------------------------------------
| Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com |
| John Wehle | Fax: 1-215-540-5495 | |
-------------------------------------------------------------------------
next reply other threads:[~1999-02-24 19:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 John Wehle [this message]
1999-02-24 19:41 ` John Wehle
1999-04-01 0:00 ` Stan Shebs
1999-02-24 19:41 ` Stan Shebs
[not found] <200003250030.TAA14328@jwlab.FEITH.COM>
2000-03-24 16:54 ` nsd
[not found] <200003242355.SAA14221@jwlab.FEITH.COM>
2000-03-24 16:08 ` nsd
-- strict thread matches above, loose matches on Subject: below --
1999-04-01 0:00 John Wehle
1999-02-25 20:48 ` John Wehle
1999-04-01 0:00 John Wehle
1999-01-20 22:33 ` John Wehle
1999-04-01 0:00 John Wehle
1999-03-09 17:07 ` John Wehle
1999-03-09 18:04 ` Stan Shebs
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 John Wehle
1999-03-09 18:39 ` John Wehle
1999-04-01 0:00 ` Stan Shebs
1999-03-09 18:57 ` Stan Shebs
1999-03-09 18:53 John Wehle
1999-04-01 0:00 ` John Wehle
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=199902250335.WAA27443@jwlab.FEITH.COM \
--to=john@feith.com \
--cc=gdb-patches@cygnus.com \
--cc=shebs@cygnus.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