public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Aaron Merey <amerey@redhat.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: [PING][PATCH 5/6 v3] gdb/debuginfod: Support on-demand debuginfo downloading
Date: Wed, 19 Jul 2023 10:33:08 -0400	[thread overview]
Message-ID: <CAJDtP-SEsR_Y0koSVzAB+j2ZaJQPN-YtH0udATrhYWuZiq6yRA@mail.gmail.com> (raw)
In-Reply-To: <CAJDtP-RXrH+nK-+N1MEGagp4LyhV5z4JGk9bmY-W3queUKVHmg@mail.gmail.com>

On Mon, Jul 10, 2023 at 5:01 PM Aaron Merey <amerey@redhat.com> wrote:
>
> On Fri, Jul 7, 2023 at 10:18 AM Andrew Burgess <aburgess@redhat.com> wrote:
> >   proc enable_section_downloads { } {
> >       global gdb_prompt
> >
> >       set cmd "maint set debuginfod download-sections on"
> >       set msg "enable section downloads"
> >
> >       return [gdb_test_multiple $cmd $msg {
> >         -re -wrap ".*not compiled into GDB.*" {
> >             return 0
> >         }
> >         -re -wrap "^" {
> >             return 1
> >         }
> >         -re -wrap "" {
> >             fail "$gdb_test_name (unexpected output)"
> >             return 0
> >         }
> >       }]
> >   }
> >
> > would do the job, though I don't currently have a machine with a recent
> > enough version of debuginfod installed to fully test this, but something
> > like this should do the job.
>
> Thanks Andrew, this works on my machine. I've updated the patch below with
> this change.

On Tue, Jul 11, 2023 at 11:00 AM Aaron Merey <amerey@redhat.com> wrote:
>
> On Tue, Jul 11, 2023 at 8:01 AM Pedro Alves <pedro@palves.net> wrote:
> >
> > Write:
> >
> >   catch (const gdb_exception &e)
> >
> > ... to avoid slicing.
> >
> > This catches QUIT exceptions as well.  Did you mean gdb_exception_error instead?
>
> Yes it should be gdb_exception_error. I've updated the patch with these changes.

Is this patch ready for merging with the above changes?

Aaron


  reply	other threads:[~2023-07-19 14:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  1:43 [PATCH 0/6 v3] gdb/debuginfod: Add " Aaron Merey
2023-06-01  1:43 ` [PATCH 1/6 v2] gdb/debuginfod: Add debuginfod_section_query Aaron Merey
2023-06-07 13:35   ` Andrew Burgess
2023-07-27 11:04     ` Andrew Burgess
2023-06-01  1:43 ` [PATCH 2/6 v2] gdb: Add command 'maint set/show debuginfod download-sections' Aaron Merey
2023-06-01  6:13   ` Eli Zaretskii
2023-06-01 22:35     ` Aaron Merey
2023-06-02  6:49       ` Eli Zaretskii
2023-06-07 13:57   ` Andrew Burgess
2023-07-27 12:04   ` Andrew Burgess
2023-07-27 12:19   ` Andrew Burgess
2023-06-01  1:43 ` [PATCH 3/6 v3] gdb: Buffer gdb_stdout during events that might download deferred debuginfo Aaron Merey
2023-06-01  6:16   ` Eli Zaretskii
2023-06-01 22:36     ` Aaron Merey
2023-06-07 13:25   ` Andrew Burgess
2023-06-01  1:43 ` [PATCH 4/6] gdb/progspace: Add reverse safe iterator and template for unwrapping iterator Aaron Merey
2023-06-15 13:44   ` Aaron Merey
2023-07-03 17:39     ` [PING*2][PATCH " Aaron Merey
2023-07-19 14:32       ` [PING*3][PATCH " Aaron Merey
2023-07-31 10:11   ` [PATCH " Andrew Burgess
2023-06-01  1:43 ` [PATCH 5/6 v3] gdb/debuginfod: Support on-demand debuginfo downloading Aaron Merey
2023-06-15 13:44   ` Aaron Merey
2023-07-03 17:39     ` [PING*2][PATCH " Aaron Merey
2023-07-07 14:18   ` [PATCH " Andrew Burgess
2023-07-10 21:01     ` Aaron Merey
2023-07-11 12:01       ` Pedro Alves
2023-07-11 15:00         ` Aaron Merey
2023-07-19 14:33           ` Aaron Merey [this message]
2023-07-27 10:24   ` Andrew Burgess
2023-06-01  1:43 ` [PATCH 6/6 v3] gdb/debuginfod: Add .debug_line downloading Aaron Merey
2023-06-15 13:45   ` Aaron Merey
2023-07-03 17:40     ` [PING*2][PATCH " Aaron Merey
2023-07-19 14:33       ` [PING*3][PATCH " Aaron Merey

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=CAJDtP-SEsR_Y0koSVzAB+j2ZaJQPN-YtH0udATrhYWuZiq6yRA@mail.gmail.com \
    --to=amerey@redhat.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).