public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <aburgess@redhat.com>,
	Simon Marchi <simark@simark.ca>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: fix missing null-character when using value_cstring
Date: Thu, 13 Apr 2023 12:56:20 +0100	[thread overview]
Message-ID: <dd725ea9-04b3-9082-3c49-994c8f6f0cec@palves.net> (raw)
In-Reply-To: <87o7nsakuf.fsf@redhat.com>

On 2023-04-12 9:47 p.m., Andrew Burgess wrote:
> Pedro Alves <pedro@palves.net> writes:

>> Hmm, this rang a bell.  See this patch and following discussion:
>>
>>  https://inbox.sourceware.org/gdb-patches/20210713153142.3957666-1-simon.marchi@efficios.com/
>>
> 
> Thanks for pointing that out.
> 
> I guess from the age of that patch it's not something you're planning to
> get back to anytime soon.  I assume you'd have no objections if I
> rebased your patch and merged it with my tests and reposted it?
> 

No objections at all.  Please feel free to use anything from it.

  reply	other threads:[~2023-04-13 11:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 21:49 Andrew Burgess
2023-04-04 13:58 ` Simon Marchi
2023-04-06 13:20   ` Andrew Burgess
2023-04-11 12:58     ` Pedro Alves
2023-04-12 20:47       ` Andrew Burgess
2023-04-13 11:56         ` Pedro Alves [this message]
2023-04-07  6:35 ` [PATCHv2] " Andrew Burgess
2023-05-24 14:10   ` [PATCHv3] gdb: building inferior strings from within GDB Andrew Burgess
2023-05-24 15:42     ` Simon Marchi
2023-06-05 12:26       ` Andrew Burgess
2023-06-05 17:57         ` Simon Marchi
2023-06-06 15:50           ` Andrew Burgess
2023-06-09 13:41             ` Tom Tromey
2023-06-09 14:20               ` Andrew Burgess

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=dd725ea9-04b3-9082-3c49-994c8f6f0cec@palves.net \
    --to=pedro@palves.net \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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).