Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [RFC][gdb/symtab] Add DEBUG_DEBUGINFOD_CLIENT in debuginfod-support.c
Date: Thu, 1 Apr 2021 09:38:11 -0400	[thread overview]
Message-ID: <89c4fbb4-e7d4-d772-c18e-ac13713188e7@polymtl.ca> (raw)
In-Reply-To: <20210331135644.GA13846@delia>

On 2021-03-31 9:56 a.m., Tom de Vries wrote:> Hi,
> 
> Add an off-by-default debug trace option DEBUG_DEBUGINFOD_CLIENT in
> debuginfod-support.c.
> 
> By redefining DEBUG_DEBUGINFOD_CLIENT to 1, we get a trace like this:
> ...
> TRYING DEBUGINFO FOR: \
>   /home/vries/gdb_versions/devel/system-supplied DSO at 0x7ffff7ffa000
> BUILDID: 157d01461677175219ab3ccd37454aeb740d2a7e
> TOOK: 0.699193 seconds
> RESULT fd: -2
> warning: Source file is more recent than executable.
> TRYING SOURCE: /home/abuild/rpmbuild/BUILD/gcc-7.5.0+r278197/\
>   obj-x86_64-suse-linux/x86_64-suse-linux/libgcc/../../../libgcc/\
>   config/i386/sfp-exceptions.c
> BUILDID: 97481d83f99d6da01138fe4c61114da27e34d17e
> TOOK: 1.724909 seconds
> RESULT fd: -2
> TRYING SOURCE: /home/abuild/rpmbuild/BUILD/gcc-7.5.0+r278197/\
>   obj-x86_64-suse-linux/x86_64-suse-linux/libgcc/../../../libgcc/libgcc2.c
> BUILDID: 97481d83f99d6da01138fe4c61114da27e34d17e
> TOOK: 0.819237 seconds
> RESULT fd: -2
> ...
> 
> Any comments?

Hi Tom,

I think this would be more useful if this was available using a "set
debug debuginfod" parameter, like the other debug printouts.

Simon

  reply	other threads:[~2021-04-01 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 13:56 Tom de Vries
2021-04-01 13:38 ` Simon Marchi via Gdb-patches [this message]
2021-04-01 16:28 ` 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=89c4fbb4-e7d4-d772-c18e-ac13713188e7@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    /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