From: Joel Brobecker <brobecker@gnat.com>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] Signal trampoline unwinder for hppa-hpux
Date: Thu, 20 May 2004 20:46:00 -0000 [thread overview]
Message-ID: <20040520204625.GB10684@gnat.com> (raw)
In-Reply-To: <20040520041746.GW566@tausq.org>
Hello Randolph,
> I tested this against hppa2.0w-hp-hpux11.11 and hppa2.0w-hp-hpux11.00,
> but I don't have a hpux machine running a 32-bit kernel to test. If
> anyone is interested in that target, please give it a try. It *should*
> work :)
How can you tell whether a kernel is 32bits or not?
I tried your patch on our machines, it we get noticeably better results,
especially in sigstep.exp, which no longer times out to death....
> 2004-05-19 Randolph Chung <tausq@debian.org>
>
> * hppa-hpux-tdep.c (offsetof): Define.
> (hppa_hpux_pc_in_sigtramp, hppa32_hpux_frame_saved_pc_in_sigtramp)
> (hppa32_hpux_frame_base_before_sigtramp)
> (hppa32_hpux_frame_find_saved_regs_in_sigtramp)
> (hppa64_hpux_frame_saved_pc_in_sigtramp)
> (hppa64_hpux_frame_base_before_sigtramp)
> (hppa64_hpux_frame_find_saved_regs_in_sigtramp): Remove unused functions.
> (hppa_hpux_sigtramp_find_sigcontext, hppa_hpux_sigtramp_unwind_cache)
> (hppa_hpux_sigtramp_frame_unwind_cache, hppa_hpux_sigtramp_frame_this_id)
> (hppa_hpux_sigtramp_frame_prev_register, hppa_hpux_sigtramp_frame_unwind)
> (hppa_hpux_sigtramp_unwind_sniffer): New signal trampoline unwinder.
> (hppa_hpux_init_abi): Register sigtramp unwinder.
--
Joel
next prev parent reply other threads:[~2004-05-20 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 4:17 Randolph Chung
2004-05-20 20:46 ` Joel Brobecker [this message]
2004-05-20 20:53 ` Randolph Chung
2004-05-20 22:36 ` Joel Brobecker
2004-05-20 23:33 ` Joel Brobecker
2004-05-21 17:41 ` Andrew Cagney
2004-05-21 18:39 ` Randolph Chung
2004-05-22 1:58 ` Randolph Chung
2004-05-23 0:29 ` Randolph Chung
2004-05-24 17:38 ` Andrew Cagney
2004-05-26 5:36 ` Randolph Chung
2004-05-26 13:20 ` Daniel Jacobowitz
2004-05-22 18:30 John David Anglin
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=20040520204625.GB10684@gnat.com \
--to=brobecker@gnat.com \
--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