Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Joel Brobecker <brobecker@adacore.com>,  gdb-patches@sourceware.org
Subject: Re: (gdb-6.8) Discard breakpoint address if shared library is unloaded
Date: Wed, 20 Feb 2008 20:27:00 -0000	[thread overview]
Message-ID: <200802202325.51341.ghost@cs.msu.su> (raw)
In-Reply-To: <18364.32147.39758.99346@kahikatea.snap.net.nz>

On Wednesday 20 February 2008 22:20:51 Nick Roberts wrote:
>  > So how about you submit a complete patch, following the usual protocol
>  > rather than an abbreviated one? I'll review it promptly, and we can
>  > put this episode behind us. As I said before, I reviewed the breakpoint.c
>  > patch and it looked fine, so it's just a matter of taking a look at
>  > the testsuite failures and adjust the testsuite accordingly (if
>  > justified).
> 
> Some or all of the other failures occur in these files:
> 
> 2007-09-23  Vladimir Prus  <vladimir@codesourcery.com>
> 	
> 	* gdb.base/annota1.exp: Adjust for 'info break'
> 	format changes.
> 	* gdb.base/annota3.exp: Likewise.
> 	* gdb.base/break.exp: Likewise.
> 	* gdb.base/condbreak.exp: Likewise.
> 	* gdb.base/pending.exp: Likewise.
> 	* gdb.base/sepdebug.exp: Likewise.
> 	* gdb.base/unload.exp: Likewise.
> 	* gdb.base/ovldbreak.exp: Likewise.
> 
> 
> So I'm surprised that Vladimir did not know there would be more than those
> in ovldbreak.exp (actually cp.base).

In my email, I've actually said I did not run the other tests and 
there might be more failures.  Getting the complete list is only
possible by running the testsuite, since I have no idea what tests were
added since then.

> It is possible for me to try to understand each of these changes and revert
> them but clearly it is far easier for Vladimir to do that as he made the
> changes in the first place.
> 
> I will try to do that but I don't have the time at the moment.

So, given that we want to release 6.8 soon, and already spent considerable time
on this patch, it looks like I get to pick up where you left. I'll try to
update the test tomorrow.

- Volodya


  reply	other threads:[~2008-02-20 20:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080204214226.GF20922@adacore.com>
2008-02-04 21:55 ` Nick Roberts
2008-02-05  0:12   ` Joel Brobecker
2008-02-05  0:21     ` Joel Brobecker
2008-02-05  0:36       ` Nick Roberts
2008-02-05  0:54     ` Nick Roberts
2008-02-07  6:38       ` Joel Brobecker
2008-02-08  1:37         ` Nick Roberts
2008-02-08  6:44           ` Vladimir Prus
2008-02-08  7:37             ` Nick Roberts
2008-02-14 21:43               ` Joel Brobecker
2008-02-15  4:01                 ` Nick Roberts
2008-02-15  8:39                   ` Eli Zaretskii
2008-02-15  9:13                     ` Nick Roberts
2008-02-16 12:59                       ` Eli Zaretskii
2008-02-17  9:56                   ` Vladimir Prus
2008-02-17 19:53                     ` Nick Roberts
2008-02-19 19:02                   ` Joel Brobecker
2008-02-19 20:04                     ` Nick Roberts
2008-02-20 16:31                       ` Joel Brobecker
2008-02-20 19:21                         ` Nick Roberts
2008-02-20 20:27                           ` Vladimir Prus [this message]
2008-02-25 10:04                             ` Vladimir Prus
2008-02-25 19:39                               ` Joel Brobecker
2008-02-26 10:03                                 ` Vladimir Prus
2008-02-26 22:55                                   ` Joel Brobecker

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=200802202325.51341.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /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