From: Jim Blandy <jimb@codesourcery.com>
To: pgilliam@us.ibm.com
Cc: Eli Zaretskii <eliz@gnu.org>,
Fabio De Bona <Auslieferator@gmx.net>,
gdb@sources.redhat.com
Subject: Re: conditional breakpoint with (char* ) string condition
Date: Mon, 15 May 2006 22:44:00 -0000 [thread overview]
Message-ID: <vt2hd3r6jm2.fsf@theseus.home.> (raw)
In-Reply-To: <20060515191808.GB5918@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 15 May 2006 15:18:08 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> On Mon, May 15, 2006 at 11:50:30AM -0700, Jim Blandy wrote:
>>
>> Daniel Jacobowitz <drow@false.org> writes:
>> > On Fri, May 12, 2006 at 11:00:16AM -0700, Jim Blandy wrote:
>> >> Should we establish a convention of starting GDB-provided convenience
>> >> variable names with _, to avoid conflicting with script variables?
>> >> Thus, $_strcmp and $_strlen?
>> >
>> > Or should they have a $gdb_ prefix? Or $_gdb_?
>>
>> Or $this_is_a_gdb_variable_20060515_GNU_prvt_ISO_IEC_9989:1999_? :)
>> (There must be some way to get a UUID and 'http' in there...)
>
> Hey, I was serious about $gdb_...
Oh. Sorry. I thought you were mocking my suggestion.
I guess I feel like we're encroaching on the user's space no matter
what we do, so we might as well make it terse. And there are are $_
variables defined by GDB already, I think. But I'd be happy with '_'
or 'gdb_'.
>> Hey, maybe we could just take over some prefix like $- that doesn't
>> conflict with the user and register namespace at all.
>
> Nice try :-)
>
> (gdb) p 2
> $1 = 2
> (gdb) p $-1
> $2 = 1
Darn. I'd forgotten $ is a token all by itself.
next prev parent reply other threads:[~2006-05-15 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 12:43 Fabio De Bona
2006-05-12 12:45 ` Eli Zaretskii
2006-05-12 13:53 ` Daniel Jacobowitz
2006-05-12 16:09 ` Eli Zaretskii
2006-05-12 16:21 ` Daniel Jacobowitz
2006-05-12 18:00 ` PAUL GILLIAM
2006-05-12 18:59 ` Jim Blandy
2006-05-15 17:55 ` Daniel Jacobowitz
2006-05-15 19:17 ` Jim Blandy
2006-05-15 19:51 ` Daniel Jacobowitz
2006-05-15 22:44 ` Jim Blandy [this message]
2006-05-16 12:39 ` Joel Brobecker
2006-05-12 20:36 ` Eli Zaretskii
2006-05-13 11:24 ` PAUL GILLIAM
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=vt2hd3r6jm2.fsf@theseus.home. \
--to=jimb@codesourcery.com \
--cc=Auslieferator@gmx.net \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=pgilliam@us.ibm.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