Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* [RFA v2 00/13] various frame filter fixes and cleanups
@ 2017-08-14  3:41 Tom Tromey
  2017-08-14  3:41 ` [RFA v2 11/13] Improve "backtrace" help text Tom Tromey
                   ` (14 more replies)
  0 siblings, 15 replies; 26+ messages in thread
From: Tom Tromey @ 2017-08-14  3:41 UTC (permalink / raw)
  To: gdb-patches

Here's version 2 of one my frame-filter-related patch series.  This
series rationalizes backtrace command-line parsing, fixes a few bugs,
and adds the ability to not print "elided" frames.

Reviews of v1 mostly were in June, e.g.:
https://sourceware.org/ml/gdb-patches/2017-06/msg00741.html
The series was posted here:
https://sourceware.org/ml/gdb-patches/2017-04/msg00671.html

I believe this new series addresses all the review comments.  However,
there have been changes and additions, so you will probably want to
re-read everything, and especially the new final patch.

There were a few questions last time.  Some are answered in specific
patches, but for the others:

[ about exceptions in py-framefilter.c ]

> Are any of these returning back to the Python runtime?  If so, then
> we can't let C++ exceptions cross it.

I think the answer is no.

> So "bt elide" means "elide the elided frames", not "show me the
> elided frames too".  It's fine with me, though I mildly wonder whether
> users will be confused by the "double negative".

"Elide" means "drop", so really "bt elide" should mean "drop whatever
frames are droppable".  Having "bt elide" mean "show the dropped
frames" would be confusing.  But maybe another word would be better
here, I don't know.

Tom



^ permalink raw reply	[flat|nested] 26+ messages in thread

end of thread, other threads:[~2017-08-14 15:10 UTC | newest]

Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-08-14  3:41 [RFA v2 00/13] various frame filter fixes and cleanups Tom Tromey
2017-08-14  3:41 ` [RFA v2 11/13] Improve "backtrace" help text Tom Tromey
2017-08-14 13:35   ` Pedro Alves
2017-08-14 14:34     ` Tom Tromey
2017-08-14 14:36       ` Pedro Alves
2017-08-14 14:38         ` Tom Tromey
2017-08-14  3:41 ` [RFA v2 13/13] Remove verbose code from backtrace command Tom Tromey
2017-08-14 13:35   ` Pedro Alves
2017-08-14  3:41 ` [RFA v2 09/13] Return EXT_LANG_BT_ERROR in one more spot in py-framefilter.c Tom Tromey
2017-08-14  3:41 ` [RFA v2 07/13] Throw a "quit" on a KeyboardException " Tom Tromey
2017-08-14  3:41 ` [RFA v2 01/13] Rationalize "backtrace" command line parsing Tom Tromey
2017-08-14 15:07   ` Eli Zaretskii
2017-08-14  3:41 ` [RFA v2 12/13] Simplify exception handling in py-framefilter.c Tom Tromey
2017-08-14 13:36   ` Pedro Alves
2017-08-14  3:41 ` [RFA v2 10/13] Call wrap_hint in one more spot " Tom Tromey
2017-08-14  3:41 ` [RFA v2 04/13] Remove EXT_LANG_BT_COMPLETED Tom Tromey
2017-08-14  3:41 ` [RFA v2 05/13] Avoid manual resource management in py-framefilter.c Tom Tromey
2017-08-14  3:41 ` [RFA v2 03/13] Allow elision of some filtered frames Tom Tromey
2017-08-14 15:10   ` Eli Zaretskii
2017-08-14  3:41 ` [RFA v2 02/13] Change backtrace_command_1 calling to use flags Tom Tromey
2017-08-14  3:41 ` [RFA v2 08/13] Move some code later in backtrace_command_1 Tom Tromey
2017-08-14  3:57 ` [RFA v2 06/13] Allow C-c to work in backtrace in more cases Tom Tromey
2017-08-14 13:20 ` [RFA v2 00/13] various frame filter fixes and cleanups Pedro Alves
2017-08-14 13:57   ` Phil Muldoon
2017-08-14 14:30     ` Pedro Alves
2017-08-14 13:38 ` Pedro Alves

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox