public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: Jonathan Wakely <jwakely@redhat.com>,
	 tom@tromey.com, gdb-testers@sourceware.org,
	 Linaro Toolchain Working Group
	<linaro-toolchain@lists.linaro.org>
Subject: Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1411-g033bc67bdb0: FAIL: 2 regressions on arm
Date: Wed, 13 Mar 2024 14:53:38 -0600	[thread overview]
Message-ID: <87h6h9x38t.fsf@tromey.com> (raw)
In-Reply-To: <30E33AC9-E689-4BD9-B862-9A1F4C018A72@linaro.org> (Maxim Kuvyrkov's message of "Wed, 13 Mar 2024 09:49:57 +0400")

>> Just a guess, but maybe making the type global instead of a local type
>> (with no linkage) will solve it:
>> 
>> --- a/libstdc++-v3/testsuite/libstdc++-prettyprinters/cxx11.cc
>> +++ b/libstdc++-v3/testsuite/libstdc++-prettyprinters/cxx11.cc
>> @@ -63,6 +63,11 @@ struct datum
>> 
>> std::unique_ptr<datum> global;
>> 
>> +struct custom_cat : std::error_category {
>> +  const char* name() const noexcept { return "miaow"; }
>> +  std::string message(int) const { return ""; }
>> +};

gdb doesn't generally handle local types well -- a longstanding bug
nobody has tried to fix.

However my patch wasn't intended to introduce this problem.
Perhaps it is at fault.

Tom

  reply	other threads:[~2024-03-13 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 19:03 ci_notify
2024-03-11 16:38 ` Maxim Kuvyrkov
2024-03-11 16:52   ` Jonathan Wakely
2024-03-13  5:49     ` Maxim Kuvyrkov
2024-03-13 20:53       ` Tom Tromey [this message]
2024-03-13 23:57         ` Jonathan Wakely

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=87h6h9x38t.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-testers@sourceware.org \
    --cc=jwakely@redhat.com \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=maxim.kuvyrkov@linaro.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).