From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: "'Tom Tromey'" <tromey@redhat.com>,
"'Daniel Jacobowitz'" <drow@false.org>,
"'gdb-patches ml'" <gdb-patches@sourceware.org>
Subject: RE: [RFA] Add la_getstr member to language_defn
Date: Thu, 05 Feb 2009 16:33:00 -0000 [thread overview]
Message-ID: <1233851589.14735.82.camel@localhost.localdomain> (raw)
In-Reply-To: <000401c987ab$bc52a520$34f7ef60$@u-strasbg.fr>
El jue, 05-02-2009 a las 17:06 +0100, Pierre Muller escribió:
> > Thiago> + Assumes strings are terminated by a null character.
> > [...]
> > Thiago> +void
> > Thiago> +c_get_string (struct value *value, gdb_byte **buffer, int
> > *length,
> > Thiago> + const char **charset)
> >
> > My understanding is that the contract for la_getstr says that the
> > resulting string will be zero-terminated. But if that is the case...
>
> But this would also mean that the string could not contain
> zero in the middle, which sometimes happens for pascal strings...
>
> Isn't the length argument there for this?
Right. The contract (the comment above la_get_string in language_defn,
assuming it is legally binding :-) ) doesn't say that the string should
be null-terminated. And the length argument doesn't count the ending
null character, should it be present.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-02-05 16:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 13:24 Thiago Jung Bauermann
2008-11-24 13:32 ` Daniel Jacobowitz
2008-11-24 14:59 ` Thiago Jung Bauermann
2008-11-24 16:19 ` Daniel Jacobowitz
2008-11-24 20:22 ` Thiago Jung Bauermann
2008-11-25 2:16 ` Daniel Jacobowitz
2008-11-25 8:53 ` Thiago Jung Bauermann
2009-01-03 2:27 ` Thiago Jung Bauermann
2009-02-02 18:42 ` Tom Tromey
2009-02-03 12:51 ` Thiago Jung Bauermann
2009-02-03 17:44 ` Tom Tromey
2009-02-04 12:37 ` Thiago Jung Bauermann
2009-02-04 19:19 ` Tom Tromey
2009-02-04 22:26 ` Thiago Jung Bauermann
2009-02-05 0:55 ` Tom Tromey
2009-02-05 12:21 ` Thiago Jung Bauermann
2009-02-05 16:01 ` Pierre Muller
2009-02-05 16:30 ` Thiago Jung Bauermann
2009-02-05 16:46 ` Tom Tromey
2009-02-05 15:55 ` Tom Tromey
2009-02-05 16:07 ` Pierre Muller
2009-02-05 16:33 ` Thiago Jung Bauermann [this message]
2009-02-05 16:46 ` Tom Tromey
2009-02-03 0:23 ` Joel Brobecker
2009-02-03 13:02 ` Thiago Jung Bauermann
2009-02-03 17:01 ` Joel Brobecker
2009-02-03 17:40 ` Tom Tromey
2009-02-05 17:01 ` Thiago Jung Bauermann
2009-02-05 23:51 ` Joel Brobecker
2008-11-24 20:03 ` Tom Tromey
2008-11-24 21:19 ` Thiago Jung Bauermann
2008-11-25 0:55 ` Tom Tromey
2008-11-25 11:27 ` Thiago Jung Bauermann
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=1233851589.14735.82.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=tromey@redhat.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