public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Alan Modra <amodra@gmail.com>
Cc: Tom Tromey <tom@tromey.com>,  Nick Clifton <nickc@redhat.com>,
	binutils@sourceware.org
Subject: Re: [PATCH 1/3] Make several more BFD globals thread-local
Date: Thu, 14 Mar 2024 19:15:06 -0600	[thread overview]
Message-ID: <87o7bguwh1.fsf@tromey.com> (raw)
In-Reply-To: <ZevhYcLMrVH41UA5@squeak.grove.modra.org> (Alan Modra's message of "Sat, 9 Mar 2024 14:41:13 +1030")

>>>>> "Alan" == Alan Modra <amodra@gmail.com> writes:

Alan> On Fri, Mar 08, 2024 at 06:12:34PM -0700, Tom Tromey wrote:
>> >>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> Also I think it'd be good if print_warnmsg re-emitted the errors using
Tom> _bfd_error_handler.  This would let gdb print them the way it likes.
Tom> However... that's a change to semantics so I don't know if that's OK or
Tom> whether another error emitter is required.  I guess I don't really know
Tom> how to provoke one of these messages and when they would matter.

Alan> See 5aa0f10c424e commit log.
Alan> The testcase in https://oss-fuzz.com/testcase-detail/4772285297328128
Alan> is the one that prompted all the messing around with errors.  Try
Alan> objdump or nm from 2.36 on that one..

Unfortunately I couldn't access it.  Is there any chance you could send
it to me so I can try it against my patch?

thanks,
Tom

  parent reply	other threads:[~2024-03-15  1:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  1:03 [PATCH 0/3] Fix some error-printing issues Tom Tromey
2024-01-30  1:03 ` [PATCH 1/3] Make several more BFD globals thread-local Tom Tromey
2024-02-12 15:28   ` Nick Clifton
2024-02-12 23:52     ` Tom Tromey
2024-02-13  0:35     ` Tom Tromey
2024-02-13  1:20       ` Tom Tromey
2024-03-09  1:12         ` Tom Tromey
2024-03-09  4:11           ` Alan Modra
2024-03-09 10:31             ` Alan Modra
2024-03-15  0:12               ` Tom Tromey
2024-03-19 20:17                 ` Tom Tromey
2024-03-15  1:15             ` Tom Tromey [this message]
2024-01-30  1:03 ` [PATCH 2/3] Do not call fputc from _bfd_doprnt Tom Tromey
2024-02-12 15:04   ` Nick Clifton
2024-01-30  1:03 ` [PATCH 3/3] Introduce bfd_print_error function Tom Tromey
2024-02-12 15:04   ` Nick Clifton

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=87o7bguwh1.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /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).