From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] Remove read_memory_string
Date: Sat, 13 Jun 2020 10:19:46 -0400 [thread overview]
Message-ID: <c3677699-c36d-e2dd-9d2f-6347d837fdb6@simark.ca> (raw)
In-Reply-To: <20200612215356.22145-2-tromey@adacore.com>
On 2020-06-12 5:53 p.m., Tom Tromey wrote:
> @@ -6721,34 +6721,38 @@ ada_get_tsd_from_tag (struct value *tag)
> The returned value is good until the next call. May return NULL
> if we are unable to determine the tag name. */
>
> -static char *
> +static gdb::unique_xmalloc_ptr<char>
> ada_tag_name_from_tsd (struct value *tsd)
The comment above needs to be updated.
> {
> - static char name[1024];
> char *p;
> struct value *val;
>
> val = ada_value_struct_elt (tsd, "expanded_name", 1);
> if (val == NULL)
> return NULL;
> - read_memory_string (value_as_address (val), name, sizeof (name) - 1);
> - for (p = name; *p != '\0'; p += 1)
> + gdb::unique_xmalloc_ptr<char> buffer;
> + int err;
> + if (target_read_string (value_as_address (val), &buffer, INT_MAX, &err) == 0
> + || err != 0)
> + return nullptr;
> +
> + for (p = (char *) buffer.get (); *p != '\0'; p += 1)
This cast is unnecessary. I'd also change `p += 1` for p++ or ++p.
The enclosing for loop should use braces, normally.
Simon
next prev parent reply other threads:[~2020-06-13 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 21:53 [PATCH 0/4] Unify string-reading APIs Tom Tromey
2020-06-12 21:53 ` [PATCH 1/4] Remove read_memory_string Tom Tromey
2020-06-13 14:19 ` Simon Marchi [this message]
2020-06-15 12:37 ` Pedro Alves
2020-06-12 21:53 ` [PATCH 2/4] Rewrite target_read_string Tom Tromey
2020-06-12 21:53 ` [PATCH 3/4] Remove a use of target_read_string Tom Tromey
2020-06-13 3:04 ` Sergio Durigan Junior
2020-06-15 12:13 ` Tom Tromey
2020-06-12 21:53 ` [PATCH 4/4] Change target_read_string API Tom Tromey
2020-06-13 14:40 ` Simon Marchi
2020-06-13 14:40 ` [PATCH 0/4] Unify string-reading APIs Simon Marchi
2020-06-15 12:27 ` Tom Tromey
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=c3677699-c36d-e2dd-9d2f-6347d837fdb6@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).