Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
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: Fri, 12 May 2006 18:00:00 -0000	[thread overview]
Message-ID: <1147446332.3672.51.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <20060512135420.GA6349@nevyn.them.org>

On Fri, 2006-05-12 at 09:54 -0400, Daniel Jacobowitz wrote:
> On Fri, May 12, 2006 at 04:49:49PM +0300, Eli Zaretskii wrote:
> > > Date: Fri, 12 May 2006 08:45:27 -0400
> > > From: Daniel Jacobowitz <drow@false.org>
> > > Cc: gdb@sources.redhat.com
> > > 
> > > I wonder.  Should we add some common builtin functions to GDB?
> > > 
> > >   b gui/R.cpp:190 if $gdb_strcmp (cmd, "train")
> > 
> > It would be nice, I think.  `streq' might be a better name, though.
> 
> Well, I'd rather have strcmp, but I agree that I botched it - I was
> going for something with the same semantics as C strcmp :-)
> 

IMHO, this is something that has been 'missing' from GDB from day 1.
Building in some common functions into GDB would be a big win.

How about strlen as well?

-=# Paul #=-


  reply	other threads:[~2006-05-12 16:09 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 [this message]
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
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=1147446332.3672.51.camel@dufur.beaverton.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=Auslieferator@gmx.net \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.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