From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sourceware.org
Subject: Re: (gdb-6.8) Discard breakpoint address if shared library is unloaded
Date: Tue, 19 Feb 2008 20:04:00 -0000 [thread overview]
Message-ID: <18363.13851.966889.923773@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080219190143.GH3713@adacore.com>
Joel Brobecker writes:
> Nick,
>
> > 2008-02-15 Nick Roberts <nickrob@snap.net.nz>
> >
> > * breakpoint.c (print_one_breakpoint_location): Revert Enb field
> > to old format. Discard breakpoint address if shared library is
> > unloaded.
> > (breakpoint_1): Adjust formatting of table header accordingly.
>
> The patch looks fine, but I assumed that you had run the testsuite
> before sending it. From my end, it looks like you didn't, and I find
> this quite disappointing. Based on Volodya's email, I ran the testsuite
> myself (which I really shouldn't have to), and discovered that your
> patch causes ~20 new failures, not just the 3 that Volodya discovered.
>
> Your patch cannot go in until the failures are investigated and fixed.
>
> Please make sure to always confirm in your submissions that you did
> run the testsuite, mentioning which architecture it was run on, and
> also confirm that it did not introduce any regression.
I did run the whole testsuite on the first patch that I submitted which, as you
pointed out, was missing some detail which I had somehow lost since last
November, but not the amendment to that patch. You might find it disappointing
that I've not rerun the testsuite but I find it disappointing that I have had
to submit complete patches for code, doumentation and testsuite to revert
changes which I pointed out broke things for Emacs.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-02-19 20:04 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 [this message]
2008-02-20 16:31 ` Joel Brobecker
2008-02-20 19:21 ` Nick Roberts
2008-02-20 20:27 ` Vladimir Prus
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=18363.13851.966889.923773@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ghost@cs.msu.su \
/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