From: Daniel Jacobowitz <dan@debian.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Richard Henderson <rth@twiddle.net>,
Zack Weinberg <zack@codesourcery.com>,
Jamie Lokier <lk@tantalophile.demon.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Set TIF_IRET in more places
Date: Tue, 7 Jan 2003 22:32:45 -0500 [thread overview]
Message-ID: <20030108033245.GA780@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0301071832210.1892-100000@home.transmeta.com>
On Tue, Jan 07, 2003 at 06:33:48PM -0800, Linus Torvalds wrote:
>
> On Tue, 7 Jan 2003, Richard Henderson wrote:
> > > We're open to better ideas ...
> >
> > Something like having dwarf2 unwind information for the
> > vsyscall page on the page as well?
>
> What would the unwind info look like? The current BK kernel will put the
> signal return into the vsyscall page, so gdb could pick up the info from
> there. But I have no idea what the unwind info looks like, or how to tell
> gdb about it.
Right now you can't, since GDB won't use the unwind info anyway; but
Richard is probably talking about MD_FALLBACK_FRAME_STATE_FOR, which is
used for exception handling unwinding instead of debugging unwinding.
Someday soon I hope to have GDB properly using this info, too.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-08 3:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 21:34 [PATCH] Set TIF_IRET in more places Zack Weinberg
2003-01-07 11:19 ` Jamie Lokier
2003-01-07 17:42 ` Linus Torvalds
2003-01-07 19:27 ` Zack Weinberg
2003-01-08 1:21 ` Richard Henderson
2003-01-08 2:33 ` Linus Torvalds
2003-01-08 3:32 ` Daniel Jacobowitz [this message]
2003-01-08 16:29 ` Jamie Lokier
2003-01-09 6:49 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 14:46 Luca Barbieri
2003-01-06 16:04 ` Linus Torvalds
2003-01-06 18:17 ` Luca Barbieri
2003-01-06 18:42 ` Ulrich Drepper
2003-01-06 18:49 ` Linus Torvalds
2003-01-06 20:26 ` Luca Barbieri
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=20030108033245.GA780@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=rth@twiddle.net \
--cc=torvalds@transmeta.com \
--cc=zack@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.