From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Strings and arrays without malloc
Date: Sun, 09 Mar 2008 22:20:00 -0000 [thread overview]
Message-ID: <ubq5nilq5.fsf@gnu.org> (raw)
In-Reply-To: <20080309161335.GA26917@caradoc.them.org> (message from Daniel Jacobowitz on Sun, 9 Mar 2008 12:13:35 -0400)
> Date: Sun, 9 Mar 2008 12:13:35 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> Index: doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.472
> diff -u -p -r1.472 gdb.texinfo
> --- doc/gdb.texinfo 3 Mar 2008 13:24:12 -0000 1.472
> +++ doc/gdb.texinfo 9 Mar 2008 15:47:34 -0000
> @@ -5567,8 +5567,10 @@ you compiled your program to include thi
> @cindex arrays in expressions
> @value{GDBN} supports array constants in expressions input by
> the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example,
> -you can use the command @code{print @{1, 2, 3@}} to build up an array in
> -memory that is @code{malloc}ed in the target program.
> +you can use the command @code{print @{1, 2, 3@}} to create an array
> +of three integers. If you pass an array to a function or assign it
> +to a program variable, @value{GDBN} copies the array to memory that
> +is @code{malloc}ed in the target program.
>
> Because C is so widespread, most of the expressions shown in examples in
> this manual are in C. @xref{Languages, , Using @value{GDBN} with Different
This part is approved. Thanks.
next prev parent reply other threads:[~2008-03-09 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 16:14 Daniel Jacobowitz
2008-03-09 22:20 ` Eli Zaretskii [this message]
2008-03-11 6:58 ` Tom Tromey
2008-03-13 6:12 ` Tom Tromey
2008-03-13 14:16 ` Thiago Jung Bauermann
2008-03-13 14:54 ` Tom Tromey
2008-03-13 16:22 ` Thiago Jung Bauermann
2008-03-13 16:59 ` Tom Tromey
2008-03-13 20:47 ` Tom Tromey
2008-03-13 19:22 ` Joel Brobecker
2008-03-21 15:03 ` 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=ubq5nilq5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--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