From: Mark Kettenis <kettenis@chello.nl>
To: Jason R Thorpe <thorpej@wasabisystems.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] i386nbsd_pc_in_sigtramp robustness
Date: Mon, 02 Sep 2002 14:39:00 -0000 [thread overview]
Message-ID: <86bs7gt6km.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Jason R Thorpe's message of "Mon, 2 Sep 2002 09:34:26 -0700"
Jason R Thorpe <thorpej@wasabisystems.com> writes:
> --3xoW37o/FfUZJwQG
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> The strategy of comparing against hard-coded addresses to find the
> signal trampoline is a bad one; it is possible for the user to change
> the VM layout, and thus the location of the signal trampoline, with a
> kernel option.
>
> The following patch changes the i386-netbsd* targets to disassemble to
> find the trampoline, as is done for other NetBSD targets.
Just a few thoughts:
* Doesn't this break things for NetBSD before 1.4? Did you consider
falling back on the old method?
* Did you notice any effect on performance? Reading from a target's
memory can be time-consuming for remote targets.
Mark
next prev parent reply other threads:[~2002-09-02 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 9:34 Jason R Thorpe
2002-09-02 14:39 ` Mark Kettenis [this message]
2002-09-02 15:13 ` Jason R Thorpe
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=86bs7gt6km.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=thorpej@wasabisystems.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