public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29316] New: gdb-add-index always generates an error when libdebuginfod wasn't compiled in
Date: Fri, 01 Jul 2022 22:29:05 +0000	[thread overview]
Message-ID: <bug-29316-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29316

            Bug ID: 29316
           Summary: gdb-add-index always generates an error when
                    libdebuginfod wasn't compiled in
           Product: gdb
           Version: 12.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: mark at klomp dot org
  Target Milestone: ---

gdb-add-index contains:

$GDB --batch -nx -iex 'set auto-load no' \
    -iex 'set debuginfod enabled off' \
    -ex "file $file" -ex "save gdb-index $dwarf5 $dir"

So it always disables debuginfod.
But gdb/debuginfod-support.c has:

/* Set callback for "set debuginfod enabled".  */ 

static void 
set_debuginfod_enabled (const char *value) 
{ 
#if defined(HAVE_LIBDEBUGINFOD) 
  debuginfod_enabled = value; 
#else 
  error (NO_IMPL); 
#endif 
}

So when not compiled against libdebuginfod that will always generate a error on
stderr.

This causes some testcase in dwz to FAIL, because any output to stderr is seen
as failure.

It also makes package build logs (if they use gdb-add-index) somewhat noisy.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-07-01 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 22:29 mark at klomp dot org [this message]
2022-07-04 20:01 ` [Bug gdb/29316] " amerey at redhat dot com
2022-07-05 22:42 ` amerey at redhat dot com
2022-07-15 21:40 ` amerey at redhat dot com

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=bug-29316-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).