From: Tom Tromey <tom@tromey.com>
To: Thiago Macieira <thiago.macieira@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Don't print NUL with "Recursive internal problem."
Date: Fri, 21 Aug 2026 09:07:24 -0600 [thread overview]
Message-ID: <8733w7tsur.fsf@tromey.com> (raw)
In-Reply-To: <20260820205605.16997-1-thiago.macieira@intel.com> (Thiago Macieira's message of "Thu, 20 Aug 2026 13:56:05 -0700")
>>>>> "Thiago" == Thiago Macieira <thiago.macieira@intel.com> writes:
Thiago> Off-by-one error. The sizeof(msg) includes the NUL character, which we
Thiago> don't want printed.
Thank you, this is ok.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2026-08-21 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 20:56 Thiago Macieira
2026-08-21 15:07 ` Tom Tromey [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=8733w7tsur.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.macieira@intel.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