From: Tom Tromey <tom@tromey.com>
To: Aaron Merey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Aaron Merey <amerey@redhat.com>
Subject: Re: [PATCH 4/7] gdb/ui-file: Add newline tracking
Date: Tue, 07 Mar 2023 13:47:47 -0700 [thread overview]
Message-ID: <87wn3sp9u4.fsf@tromey.com> (raw)
In-Reply-To: <CAJDtP-R=G2kOqA-Riak135tL5i+88BreyJ1Sgfab8wsXMFU6kA@mail.gmail.com> (Aaron Merey via Gdb-patches's message of "Tue, 7 Mar 2023 15:30:01 -0500")
>>>>> "Aaron" == Aaron Merey via Gdb-patches <gdb-patches@sourceware.org> writes:
Aaron> On Tue, Mar 7, 2023 at 2:34 PM Tom Tromey <tom@tromey.com> wrote:
Aaron> (gdb) backtrace
Aaron> [...]
Aaron> #8 0x00007fbe8af7d7cf in pygi_invoke_c_callable (
Aaron> Downloading separate debug info for /lib64/libpython3.11.so.1.0
Aaron> function_cache=0x561221b224d0, state=<optimized out>...
>> Still kind of badly formatted though?
>> A long time ago, IIRC, the backtrace code had a second loop to do some
>> unwinding precisely to cause debuginfo to be loaded. I wonder if it
>> makes sense to resurrect this idea. It's unclear if this would work
>> with frame filters though.
Aaron> Can we accumulate the backtrace output in a buffer and print the whole
Aaron> thing in one shot after all frames have been computed/filtered? Then all
Aaron> debuginfod messages would print together, followed by the uninterrupted
Aaron> backtrace.
I like this idea.
To make it still seem "incremental", it seems like we'd only need to
print a single frame to a ui_file. Then after that frame is done, the
buffer can be printed and gdb can move on to the next one.
Tom
next prev parent reply other threads:[~2023-03-07 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 19:42 [PATCH 1/7] gdb/debuginfod: Add debuginfod_section_query Aaron Merey
2023-02-27 19:42 ` [PATCH 2/7] gdb: add 'lazy' setting for command 'set debuginfod enabled' Aaron Merey
2023-02-27 19:54 ` Eli Zaretskii
2023-05-24 9:31 ` Andrew Burgess
2023-02-27 19:42 ` [PATCH 3/7] gdb/debuginfod: disable pagination during downloads Aaron Merey
2023-03-03 21:33 ` Tom Tromey
2023-03-06 23:07 ` Aaron Merey
2023-05-24 9:38 ` Andrew Burgess
2023-05-24 18:57 ` Aaron Merey
2023-02-27 19:42 ` [PATCH 4/7] gdb/ui-file: Add newline tracking Aaron Merey
2023-03-07 19:33 ` Tom Tromey
2023-03-07 20:30 ` Aaron Merey
2023-03-07 20:47 ` Tom Tromey [this message]
2023-02-27 19:42 ` [PATCH 5/7] gdb/debuginfod: Support on-demand debuginfo downloading Aaron Merey
2023-03-07 20:20 ` Tom Tromey
2023-03-09 0:22 ` Aaron Merey
2023-02-27 19:42 ` [PATCH 6/7] gdb/testsuite/gdb.debuginfod: Add lazy downloading tests Aaron Merey
2023-05-02 15:48 ` Andrew Burgess
2023-05-02 16:24 ` Aaron Merey
2023-05-24 10:12 ` Andrew Burgess
2023-02-27 19:42 ` [PATCH 7/7] gdb/debuginfod: Add .debug_line downloading Aaron Merey
2023-03-07 20:36 ` Tom Tromey
2023-03-09 0:26 ` Aaron Merey
2023-02-28 11:11 ` [PATCH 1/7] gdb/debuginfod: Add debuginfod_section_query Alexandra Petlanova Hajkova
2023-05-24 9:01 ` Andrew Burgess
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=87wn3sp9u4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amerey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).