From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Tom Tromey <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] remove ECOFF
Date: Tue, 20 Aug 2013 15:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1308201512490.15834@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.1.10.1308191948550.8514@tp.orcam.me.uk>
On Mon, 19 Aug 2013, Maciej W. Rozycki wrote:
> We have kept maintaining bare-iron MIPS PDR support in CodeBench and my
> intent is to enable it for Linux MIPS targets, add the heuristic outlined
> above and resurrect the old code GDB used to have with the improvements
> included. Without that debugging is often a challenge -- while the
> heuristic unwinders are good enough to handle stepping in to a function
> that has no debug information so that it's skipped over with the usual
> `step' or `next' CLI operations (and their MI equivalents), interrupting a
> program randomly within a function that has no debug information -- a
> common scenario e.g. where a Linux process is sleeping in a syscall
> invoked from stripped libc -- provides the user with no backtrace and
> therefore no access to any local state or the ability to control execution
> other than by instruction-level stepping (`stepi' or `nexti').
Rather than resurrecting this legacy MIPS-specific support, it would seem
a lot better on Linux to generate .eh_frame by default (as on various
other architectures) and phase out any remaining PDR generation there.
For glibc 2.18 the eh_frame CFI information is present in many assembly
sources and it could be added to the rest.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2013-08-20 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 18:19 Tom Tromey
2013-08-19 18:51 ` Mark Kettenis
2013-08-19 18:57 ` Tom Tromey
2013-08-19 19:02 ` Tom Tromey
2013-08-19 19:41 ` Joel Brobecker
2013-08-19 21:21 ` Maciej W. Rozycki
2013-08-19 23:22 ` Stan Shebs
2013-08-20 15:12 ` Tom Tromey
2013-08-20 15:20 ` Mark Kettenis
2013-08-20 16:19 ` Maciej W. Rozycki
2013-08-20 15:19 ` Joseph S. Myers [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=Pine.LNX.4.64.1308201512490.15834@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@codesourcery.com \
--cc=tromey@redhat.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