public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug find-debuginfo/30505] unchecked "debugedit" "gdb-add-index" "strip_to_debug" "add_minidebug" invocation
Date: Tue, 20 Aug 2024 15:01:07 +0000	[thread overview]
Message-ID: <bug-30505-13298-ZmXwOKbJrM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30505-13298@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|unchecked "gdb-add-index"   |unchecked "debugedit"
                   |invocation                  |"gdb-add-index"
                   |                            |"strip_to_debug"
                   |                            |"add_minidebug" invocation

--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
Although the above patch now propagates the errors from gdb-add-index, there
are still some other places that "hide" errors. The main debugedit invocation,
strip_to_debug, add_minidebug.

So keeping this bug open for now to track we handle those too.

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

      parent reply	other threads:[~2024-08-20 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 11:04 [Bug find-debuginfo/30505] New: unchecked "gdb-add-index" invocation lersek at redhat dot com
2023-06-01 11:27 ` [Bug find-debuginfo/30505] " mark at klomp dot org
2023-12-10 22:16 ` mark at klomp dot org
2024-08-16 18:58 ` keiths at redhat dot com
2024-08-20 14:56 ` mark at klomp dot org
2024-08-20 15:01 ` mark at klomp dot org [this message]

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-30505-13298-ZmXwOKbJrM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=debugedit@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).