Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <ARistovski@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
	 	gdb-patches@sources.redhat.com, nickrob@snap.net.nz
Subject: Re: [patch] fix for PR2424
Date: Tue, 15 Apr 2008 15:07:00 -0000	[thread overview]
Message-ID: <4804BF23.10505@qnx.com> (raw)

Daniel Jacobowitz wrote:
> On Mon, Apr 14, 2008 at 10:41:38AM -0400, Aleksandar Ristovski wrote:
>> ping?
> 
> Thanks.  The most recent version of this patch (code + testsuite) is OK.
> 
> Please mention the PR at the top of the changelog entry, like this:
> 
> DATE  NAME  <ADDR>
> 
> 	PR gdb/2424
> 	* infrun.c (some change): ....
> 
> Then if you include that line in the commit message, the changelog
> entry is automatically appended to the PR audit trail.
> 
> Shouldn't the disp="del" field be described in the manual?  If so,
> that can be a separate patch.
> 
Committed.

NOTE1 (reminder): With this patch, we have new field in the *stopped
message, 
when "reason == breakpoint-hit" - we will have "disp" field printed; the
value 
of the field will be exactly the same as the value printed when the
breakpoint 
was created.

NOTE2: Due to quite significant rework of certain functions in
mi-support.exp, 
committed diff for testsuite is not exactly the same as the one I posted. I
took 
liberty to commit anyway since the changes are functionally the same; note
the 
slightly awkward syntax for "mi_expect_stop" call, namely the "extra"
argument 
which now must be something like { "" "disp=\"keep\"" } - I don't think it's
too 
bad (it can be beautified later).

NOTE3: In mi-support.exp (mi_expect_stop), I put argument "after_reason" to
be 
after the reason (I couldn't find it being used anywhere anyway, so this
should 
be a safe change).

NOTE4: Documentation is not updated (I will try to do that now and submit
the 
diff for approval).

Thanks,

Aleksandar Ristovski
QNX Software Systems


             reply	other threads:[~2008-04-15 14:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 15:07 Aleksandar Ristovski [this message]
2008-04-15 15:25 ` Daniel Jacobowitz
2008-04-16 13:17 ` Vladimir Prus
2008-04-23 11:16 ` Vladimir Prus
  -- strict thread matches above, loose matches on Subject: below --
2008-04-23 17:48 Aleksandar Ristovski
2008-04-23 17:49 ` Vladimir Prus
2008-04-16 18:28 Aleksandar Ristovski
2008-04-15 15:31 Aleksandar Ristovski
2008-04-14 15:16 Aleksandar Ristovski
2008-04-14 18:06 ` Daniel Jacobowitz
2008-04-01 19:41 Aleksandar Ristovski
2008-03-05 17:36 Aleksandar Ristovski
2008-03-08 11:31 ` Nick Roberts
2008-03-08 18:36 ` Vladimir Prus
2008-03-09  0:12   ` Aleksandar Ristovski
2008-03-09  3:32     ` Nick Roberts
2008-03-09  4:55       ` Aleksandar Ristovski
2008-03-10  8:11     ` Vladimir Prus
2008-03-10 14:29       ` Aleksandar Ristovski
2008-03-10 14:45         ` Vladimir Prus
2008-03-10 17:18           ` Aleksandar Ristovski
2008-03-10 17:36             ` Vladimir Prus
2008-03-10 18:50               ` Aleksandar Ristovski

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=4804BF23.10505@qnx.com \
    --to=aristovski@qnx.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    --cc=vladimir@codesourcery.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