Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix for pending breakpoints in manually loaded/unloaded shlibs
Date: Wed, 01 Sep 2004 20:44:00 -0000	[thread overview]
Message-ID: <41363482.7030204@redhat.com> (raw)
In-Reply-To: <41362333.nail1N211MB10@mindspring.com>

[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]

Michael Chastain wrote:
> Jeff Johnston <jjohnstn@redhat.com> wrote:
> 
>>Thanks.  Patches committed, including fix to the testcase.
> 
> 
> Uh, I haven't approved that fix.
> 
> I wrote:
> 
>   If the test script accepts both old+new messages, and the new message is
>   not wildly more complex than the old message, then testing with the old
>   message alone is good enough for getting the test script approved.
>   Just pop out the new patch and say how / what system you tested on.
>    
> You needed to send a fresh patch to gdb-patches, say how you tested it,
> and then get it approved.  I'm sorry if this wasn't clear from my message.
> Sometimes I do write too colloquially.
> 
> This is actually a live issue because the patch you committed has
> a problem:
> 
>   -"Continuing.*y is 7.*warning: Temporarily disabling unloaded shared library breakpoints.*warning: breakpoint #.*Program exited normally." \
>   -"continuing to end of program second time"
>   +"Continuing.*y is 7.*warning: Temporarily disabling breakpoints for.*unloadshr.sl.*Program exited normally." \
>   +"continuing to end of program"
> 
> Now there are two tests with the identical name "continuing to end
> of program", which leads to confusion.
> 
> Can you please: fix that; say which system you tested it on;
> and submit a patch to gdb-patches?
>

Oops, my bad.  Sorry about that.

Tested on x86-linux, ia64-linux, x86_64-linux, s390-linux.

Patch attached to fix problem above.

2004-09-01  Jeff Johnston  <jjohnstn@redhat.com>

         * gdb.base/unload.exp: Fix so messages aren't duplicated.


> Michael
> 

[-- Attachment #2: unload.patch3 --]
[-- Type: text/plain, Size: 562 bytes --]

Index: gdb.base/unload.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/unload.exp,v
retrieving revision 1.2
diff -u -p -r1.2 unload.exp
--- gdb.base/unload.exp	1 Sep 2004 17:56:20 -0000	1.2
+++ gdb.base/unload.exp	1 Sep 2004 20:40:57 -0000
@@ -139,5 +139,5 @@ gdb_test "run" \
 
 gdb_test "continue" \
 "Continuing.*y is 7.*warning: Temporarily disabling breakpoints for.*unloadshr.sl.*Program exited normally." \
-"continuing to end of program"
+"continuing to end of program second time"
 

  reply	other threads:[~2004-09-01 20:44 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 19:09 Jeff Johnston
2004-08-10 19:45 ` Kevin Buettner
2004-08-11  4:07 ` Eli Zaretskii
2004-08-11 15:58   ` Jeff Johnston
2004-08-11 16:58     ` Andrew Cagney
2004-08-11 17:59       ` Eli Zaretskii
2004-08-11 20:42         ` Andrew Cagney
2004-08-11 20:47           ` Daniel Jacobowitz
2004-08-11 22:19             ` Andrew Cagney
2004-08-12 12:58               ` Daniel Jacobowitz
2004-08-12 13:16                 ` New observer objfile_mapped; was Andrew Cagney
2004-08-12 13:18                   ` Daniel Jacobowitz
2004-08-12  3:45           ` [RFA]: Fix for pending breakpoints in manually loaded/unloaded shlibs Eli Zaretskii
2004-08-12 12:10             ` Andrew Cagney
2004-08-12 18:49               ` Eli Zaretskii
2004-08-12 20:44                 ` Andrew Cagney
2004-08-14 11:50                   ` Eli Zaretskii
2004-08-18 13:45                     ` Daniel Jacobowitz
2004-08-19  3:57                       ` Eli Zaretskii
2004-08-11  8:09 ` Michael Chastain
2004-08-11 15:42   ` Jeff Johnston
2004-08-12 13:05     ` Michael Chastain
2004-08-12 13:33     ` Michael Chastain
2004-08-12 17:47       ` Jeff Johnston
2004-08-12 18:59         ` Michael Chastain
2004-08-12 20:23           ` Jeff Johnston
2004-08-11 17:12 ` Daniel Jacobowitz
2004-08-11 20:12   ` Jeff Johnston
2004-08-18 13:56     ` Daniel Jacobowitz
2004-08-18 19:22       ` Jeff Johnston
2004-08-18 19:39         ` Daniel Jacobowitz
2004-08-18 20:03           ` Jeff Johnston
2004-08-19  4:01             ` Eli Zaretskii
2004-09-01 15:15               ` Andrew Cagney
2004-09-01 18:01                 ` Jeff Johnston
2004-09-01 19:30                   ` Michael Chastain
2004-09-01 20:44                     ` Jeff Johnston [this message]
2004-09-01 20:59                       ` Michael Chastain
2004-09-01 23:27                         ` Jeff Johnston
2004-09-02  3:54                 ` Eli Zaretskii
2004-08-23 21:33             ` Jeff Johnston
2004-08-23 22:09               ` Michael Chastain
2004-08-23 22:35                 ` Jeff Johnston
2004-08-24  2:26                   ` Michael Chastain
2004-08-24 15:51                     ` Jeff Johnston
2004-08-24 16:04                       ` Michael Chastain
2004-08-12  2:48 ` Andrew Cagney
2004-08-12  3:54   ` Eli Zaretskii

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=41363482.7030204@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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