From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add switch to disable DWARF stack unwinders
Date: Sat, 14 Jul 2018 20:36:00 -0000 [thread overview]
Message-ID: <20180714203633.GD2888@embecosm.com> (raw)
In-Reply-To: <8736wmbv6o.fsf@tromey.com>
* Tom Tromey <tom@tromey.com> [2018-07-13 16:57:35 -0600]:
> >>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
>
> Andrew> That said, if there is a wider interest in having this ability I'm
> Andrew> happy to dig out my old branch and get it ready for submission, but
> Andrew> I'd only want to put that effort in if this was a feature people would
> Andrew> like to see in GDB...
>
> Yeah, I am not sure, your patch just reminded me of this.
>
> Maybe if the DWARF patch goes in, the bug could be closed.
> Given its age I would suppose this hasn't been needed very often.
>
> Relatedly, somewhere I have a patch that adds a name to every unwinder,
> so that you can tell what made the frame you're looking at. This can be
> handy when debugging unwinders.
Great minds... :)
I have a similar patch as part of my "make all unwinders switchable"
series. I agree it's a nice feature to be able to see who unwound
each frame.
Maybe I should clean it up and submit it...
Thanks,
Andrew
>
> Tom
next prev parent reply other threads:[~2018-07-14 20:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 13:46 Andrew Burgess
2018-07-13 13:54 ` Eli Zaretskii
2018-07-13 15:34 ` Tom Tromey
2018-07-13 22:37 ` Andrew Burgess
2018-07-13 22:57 ` Tom Tromey
2018-07-14 20:36 ` Andrew Burgess [this message]
2018-07-16 15:34 ` Tom Tromey
2018-07-14 1:11 ` Simon Marchi
2018-07-14 20:35 ` Andrew Burgess
2018-07-14 21:39 ` Simon Marchi
2018-07-17 13:23 ` Pedro Alves
2018-07-17 13:36 ` Pedro Alves
2018-07-25 15:18 ` [PATCHv2] " Andrew Burgess
2018-07-25 17:09 ` Eli Zaretskii
2018-07-25 20:07 ` Tom Tromey
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=20180714203633.GD2888@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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