From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] sigaltstack fixes for hppa-linux
Date: Fri, 07 May 2004 15:44:00 -0000 [thread overview]
Message-ID: <409BAECA.8010607@gnu.org> (raw)
In-Reply-To: <20040507150758.GJ3965@tausq.org>
>>> well, only because the hppa sigtramp unwinder is slightly broken :-) for
>>> the sigtramp frame it current uses the sp stored in the sigcontext as
>>> the frame base. instead it should probably use the handler's stack.
>
>
> here's a fixed version. No frame.c modifications needed :)
>
> one question related to this: i noticed that some of the tests are
> failing when:
> - a breakpoint is placed in the signal trampoline (e.g. "finish" from
> the signal handler)
> - we try to unwind from the signal trampoline frame
>
> they fail because breakpoints are not yet disabled when the unwinding
> starts (get_frame_id() is called early on in handle_inferior_event,
> which runs through the unwinders)
>
> Are the unwinders that do code matching supposed to deal with the case
> where there are breakpoints inserted in the code stream? or does this
> point to something else that is broken?
Yes, use frame*memory* and it will work (see tramp-frame.c:
tramp_frame_start()) (and yes, having those memory routines possibly
include breakpoints is just weird).
Feel free to fix any other HP unwinders with a follow-on commit.
Some suggested tweaks before committing follow:
> 2004-05-06 Randolph Chung <tausq@debian.org>
>
> * hppa-linux-tdep.c (hppa_linux_sigtramp_find_sigcontext): Pass in pc
> instead of sp, handle sigaltstack case.
> (hppa_linux_sigtramp_frame_unwind_cache): Adjust calls to
> hppa_linux_sigtramp_find_sigcontext, and set base to the frame of the
> signal handler and not that of the caller.
> (hppa_linux_sigtramp_unwind_sniffer): Adjust calls to
> hppa_linux_sigtramp_find_sigcontext.
>
> Index: hppa-linux-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/hppa-linux-tdep.c,v
> retrieving revision 1.2
> diff -u -p -r1.2 hppa-linux-tdep.c
> --- hppa-linux-tdep.c 7 May 2004 05:48:49 -0000 1.2
> +++ hppa-linux-tdep.c 7 May 2004 06:24:07 -0000
> @@ -282,7 +284,7 @@ hppa_linux_skip_trampoline_code (CORE_AD
> Note that with a 2.4 64-bit kernel, the signal context is not properly
> passed back to userspace so the unwind will not work correctly. */
> static CORE_ADDR
> -hppa_linux_sigtramp_find_sigcontext (CORE_ADDR sp)
> +hppa_linux_sigtramp_find_sigcontext (CORE_ADDR pc)
> {
> unsigned int dummy[HPPA_MAX_INSN_PATTERN_LEN];
> int offs = 0;
> @@ -291,6 +293,12 @@ hppa_linux_sigtramp_find_sigcontext (COR
> static int pcoffs[] = { 0, 4*4, 5*4 };
> /* offsets to the rt_sigframe structure */
> static int sfoffs[] = { 4*4, 10*4, 10*4 };
> + CORE_ADDR sp;
> +
> + /* Most of the time, this will be correct. The one case when this will
> + fail is if the user defined an alternate stack, in which case the
> + beginning of the stack will not be pc & 63. */
> + sp = (pc & ~63);
Use align_down() (I never trust C's sign extension rules).
Andrew
prev parent reply other threads:[~2004-05-07 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 15:02 Randolph Chung
2004-05-07 1:19 ` Andrew Cagney
2004-05-07 2:36 ` Randolph Chung
2004-05-07 15:07 ` Randolph Chung
2004-05-07 15:44 ` Andrew Cagney [this message]
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=409BAECA.8010607@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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