From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: cagney@gnu.org, eliz@elta.co.il, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <yf2oequw1dk.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040318162402.A32E34B104@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Thu, 18 Mar 2004 11:24:02 -0500 (EST)")
On Thu, 18 Mar 2004 11:24:02 -0500 (EST), mec.gnu@mindspring.com
(Michael Elizabeth Chastain) said:
> The actual part of PROBLEMS that you're objecting to is the
> paragraphs which talk about setting breakpoints in constructors in
> C++ code. This doesn't work with gcc v3 because gcc v3 emits
> multiple copies of the object code, and gdb sets the breakpoint in
> just one of them.
> Before PROBLEMS talked about this, we got several reports per month
> about this issue. Now we don't get any. And for each user that
> takes the trouble to e-mail us, there are many more users who run
> into the issue and appreciate having a short description of it.
> I think we should keep that part of PROBLEMS as long as gdb has this
> problem.
I agree. I can see the point of mentioning fiddling little
regressions once in PROBLEMS and then deleting the entry on subsequent
releases, even if the regressions remain. But it makes sense to me to
leave important, frequently encountered bugs in PROBLEMS.
David Carlton
carlton@kealia.com
WARNING: multiple messages have this Message-ID
From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: cagney@gnu.org, eliz@elta.co.il, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Thu, 18 Mar 2004 16:45:00 -0000 [thread overview]
Message-ID: <yf2oequw1dk.fsf@hawaii.kealia.com> (raw)
Message-ID: <20040318164500.2iU-EnIJktUMWk-B-Bo-hO9dF-wRT1VMyRBSBKAw4fA@z> (raw)
In-Reply-To: <20040318162402.A32E34B104@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Thu, 18 Mar 2004 11:24:02 -0500 (EST)")
On Thu, 18 Mar 2004 11:24:02 -0500 (EST), mec.gnu@mindspring.com
(Michael Elizabeth Chastain) said:
> The actual part of PROBLEMS that you're objecting to is the
> paragraphs which talk about setting breakpoints in constructors in
> C++ code. This doesn't work with gcc v3 because gcc v3 emits
> multiple copies of the object code, and gdb sets the breakpoint in
> just one of them.
> Before PROBLEMS talked about this, we got several reports per month
> about this issue. Now we don't get any. And for each user that
> takes the trouble to e-mail us, there are many more users who run
> into the issue and appreciate having a short description of it.
> I think we should keep that part of PROBLEMS as long as gdb has this
> problem.
I agree. I can see the point of mentioning fiddling little
regressions once in PROBLEMS and then deleting the entry on subsequent
releases, even if the regressions remain. But it makes sense to me to
leave important, frequently encountered bugs in PROBLEMS.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-03-18 16:45 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-18 16:23 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:27 ` Daniel Jacobowitz
2004-03-19 14:56 ` Eli Zaretskii
2004-03-19 15:03 ` Andrew Cagney
2004-03-19 15:33 ` Eli Zaretskii
2004-03-19 15:54 ` Andrew Cagney
2004-03-20 15:38 ` Eli Zaretskii
2004-03-19 0:09 ` David Carlton [this message]
2004-03-18 16:45 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 6:58 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 19:30 ` Michael Elizabeth Chastain
2004-03-17 19:48 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 6:06 ` Eli Zaretskii
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 20:15 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 19:21 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 18:21 ` Michael Elizabeth Chastain
2004-03-17 22:11 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 22:54 Michael Elizabeth Chastain
2004-03-17 23:39 ` Andrew Cagney
2004-03-18 6:16 ` Eli Zaretskii
2004-03-18 16:05 ` Andrew Cagney
2004-03-18 16:52 ` Eli Zaretskii
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-17 18:55 Michael Elizabeth Chastain
2004-03-17 19:03 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-17 19:16 ` David Carlton
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-17 1:53 Michael Elizabeth Chastain
2004-03-17 16:13 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 17:05 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` David Carlton
2004-03-17 17:19 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-17 19:07 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 22:11 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 6:11 ` Eli Zaretskii
2004-03-18 16:36 ` Daniel Jacobowitz
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 16:55 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:25 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` David Carlton
2004-03-17 19:18 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-17 6:16 ` 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=yf2oequw1dk.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=cagney@gnu.org \
--cc=eliz@elta.co.il \
--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