Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Tom Tromey'" <tromey@redhat.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: RE: [patch] MI ignores conditions for pending breakpoints
Date: Wed, 25 Jul 2012 18:38:00 -0000	[thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5C250033AD@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <877gtrhexk.fsf@fleche.redhat.com>

> -----Original Message-----
> From: Tom Tromey [mailto:tromey@redhat.com] 
> Sent: Wednesday, July 25, 2012 2:30 PM
> To: Marc Khouzam
> Cc: 'gdb-patches@sourceware.org'
> Subject: Re: [patch] MI ignores conditions for pending breakpoints
> 
> >>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:
> 
> Marc> Thanks for that.  I've also added a check to make sure x==4 when
> Marc> the breakpoint hits.  How about this?
> 
> Ok.

Committed to HEAD.

> 
> Marc> P.S. To save time, is there a good way to run a single 
> test while
> Marc> writing it?
> 
> What I do is
> 
>    cd build/gdb/testsuite
>    runtest whatever.exp

Awesome!  That's what I needed.

> "make check RUNTESTFLAGS=whatever.exp" also works but is wordier.
> 
> You can also run just a single directory with
> 
>    runtest --directory=gdb.python

I didn't know that, but I found this one (slightly faster to type):
  make check-gdb.python

Thanks!

Marc


      reply	other threads:[~2012-07-25 18:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-21  3:04 Marc Khouzam
2012-07-23 19:08 ` Tom Tromey
2012-07-24 17:42   ` Marc Khouzam
2012-07-25 13:11     ` Marc Khouzam
2012-07-25 15:50       ` Tom Tromey
2012-07-25 17:45         ` Marc Khouzam
2012-07-25 17:49           ` Tom Tromey
2012-07-25 18:26             ` Marc Khouzam
2012-07-25 18:43               ` Tom Tromey
2012-07-25 18:38                 ` Marc Khouzam [this message]

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=F7CE05678329534C957159168FA70DEC5C250033AD@EUSAACMS0703.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --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