Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: gdb-patches@sourceware.org
Subject: Re: [ob] More warnings; Call for assistance
Date: Wed, 18 Jan 2006 01:15:00 -0000	[thread overview]
Message-ID: <8f2776cb0601171715h4afaf38cm6e25b1983e73b1a9@mail.gmail.com> (raw)
In-Reply-To: <20060117151730.GA2420@nevyn.them.org>

On 1/17/06, Daniel Jacobowitz <drow@false.org> wrote:
> LA_PRINT_STRING takes a const gdb_byte * argument for the string.  But this
> is a NUL-terminated string in the debugger's memory; I think stepping back
> to char * is the best fix here.  That's the expprint.c warnings.

I wrote that up, but then I didn't like it.  The use of 'char *'
should be reserved for host-format character strings, but it looks to
me like LA_PRINT_STRING expects a string in the target format.  (Not
that the interface documentation offers much help here.)  Look at the
way c_printstr unpacks the string character by character using
extract_unsigned_integer.  Look at the way LA_EMIT_CHAR is responsible
for calling target_char_to_host.

If folks agree, then I'll make the comments in language.h clearer, and
try to finish off this change.


  parent reply	other threads:[~2006-01-18  1:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 15:17 Daniel Jacobowitz
2006-01-17 15:22 ` Daniel Jacobowitz
2006-01-17 19:37   ` Jim Blandy
2006-01-17 19:46     ` Daniel Jacobowitz
2006-01-17 20:11       ` Eli Zaretskii
2006-01-20 23:06         ` Daniel Jacobowitz
2006-01-21 10:07           ` Eli Zaretskii
2006-01-21 15:18             ` Daniel Jacobowitz
2006-01-17 20:57       ` Jim Blandy
2006-01-17 20:17     ` Eli Zaretskii
2006-01-20 23:09   ` Daniel Jacobowitz
2006-01-17 20:19 ` Eli Zaretskii
2006-01-17 20:23   ` Daniel Jacobowitz
2006-01-17 21:08     ` Eli Zaretskii
2006-01-17 21:14       ` Daniel Jacobowitz
2006-01-18  4:16         ` Eli Zaretskii
2006-01-18  1:15 ` Jim Blandy [this message]
2006-01-18 23:33   ` Daniel Jacobowitz

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=8f2776cb0601171715h4afaf38cm6e25b1983e73b1a9@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sourceware.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