linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: David.Mosberger@acm.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix vsyscall unwind information
Date: Mon, 5 May 2003 09:34:44 -0700	[thread overview]
Message-ID: <20030505163444.GB9342@twiddle.net> (raw)
In-Reply-To: <16054.32214.804891.702812@panda.mostang.com>

On Mon, May 05, 2003 at 08:05:58AM -0700, David Mosberger-Tang wrote:
>   Richard> Why?  Certainly it isn't needed for x86.
> 
> Certain applications (such as debuggers) want to know.  Sure, you can
> do symbol matching (if you have the symbol table) or code-reading
> (assuming you know the exact sigreturn sequence), but having a marker
> would be more reliable and faster.

Eh.  The whole point was to *eliminate* the special cases.

If the debugger does nothing special now, it'll see the symbol
from the VDSO in the backtrace and print __kernel_sigreturn.
Isn't this sufficient for the user to recognize what's going on?
Does it really need to print <signal frame>?



r~

  reply	other threads:[~2003-05-05 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030502004014$08e2@gated-at.bofh.it>
     [not found] ` <20030503210015$292c@gated-at.bofh.it>
     [not found]   ` <20030504063010$279f@gated-at.bofh.it>
2003-05-05  6:49     ` David Mosberger-Tang
2003-05-05  7:42       ` Richard Henderson
2003-05-05 15:05         ` David Mosberger-Tang
2003-05-05 16:34           ` Richard Henderson [this message]
2003-05-05 16:55             ` David Mosberger-Tang
2003-05-05 23:10             ` Mark Kettenis
2003-05-06  0:21               ` Richard Henderson
2003-05-06  6:16                 ` David Mosberger-Tang
2003-05-02  0:33 [PATCH] i386 vsyscall DSO implementation, take 2 Roland McGrath
2003-05-03 20:51 ` Richard Henderson
2003-05-04  6:21   ` [PATCH] fix vsyscall unwind information Richard Henderson
2003-05-04  7:34     ` Ulrich Drepper

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=20030505163444.GB9342@twiddle.net \
    --to=rth@twiddle.net \
    --cc=David.Mosberger@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] fix vsyscall unwind information' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).