From: "H . J . Lu" <hjl@lucon.org>
To: gdb@sources.redhat.com
Subject: Re: gdb 5.2 removes the conditional breakpoints
Date: Thu, 18 Apr 2002 10:34:00 -0000 [thread overview]
Message-ID: <20020418103444.A21869@lucon.org> (raw)
In-Reply-To: <20020418132323.A25488@nevyn.them.org>; from drow@mvista.com on Thu, Apr 18, 2002 at 01:23:24PM -0400
On Thu, Apr 18, 2002 at 01:23:24PM -0400, Daniel Jacobowitz wrote:
> On Thu, Apr 18, 2002 at 09:30:59AM -0700, H . J . Lu wrote:
> > On Thu, Apr 18, 2002 at 02:08:41PM +0300, Eli Zaretskii wrote:
> > >
> > > On Thu, 18 Apr 2002, Michael Veksler wrote:
> > >
> > > > Your argument that "5,2 has been around for ~4
> > > > years" does not hold water, how many people have been using 5.2 ?
> > >
> > > You misunderstood: Andrew said that between 4.17 and 5.2, all versions of
> > > GDB had this bug. Those versions in between are in use for 4 years, not
> > > version 5.2 (which wasn't released yet).
> > >
> >
> > Between 4.17 and 5.2, 4.18 and 5.0 are basically broken for Linux. I
> > only started using 5.1 a few months ago. For me, this regression is
> > relatively new to my gdb.
>
> That's just untrue. I used both 4.18 and 5.0 extensively on GNU/Linux
> systems, and they worked quite well.
>
Are you using linuxthreads and hardware watchpoints? Here is one thread
on this:
http://sources.redhat.com/ml/gdb/2001-09/msg00138.html
H.J.
next prev parent reply other threads:[~2002-04-18 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 23:40 Michael Veksler
2002-04-18 3:11 ` Eli Zaretskii
2002-04-18 9:31 ` H . J . Lu
2002-04-18 10:22 ` Daniel Jacobowitz
2002-04-18 10:34 ` H . J . Lu [this message]
2002-04-18 10:41 ` Daniel Jacobowitz
2002-04-18 9:42 ` H . J . Lu
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 0:52 Michael Veksler
2002-04-17 16:57 ` H . J . Lu
2002-04-17 17:34 ` Andrew Cagney
2002-04-17 17:48 ` H . J . Lu
2002-04-17 20:20 ` Andrew Cagney
2002-03-22 9:50 H . J . Lu
2002-03-22 10:24 ` Andrew Cagney
2002-03-22 10:45 ` H . J . Lu
2002-03-22 10:27 ` Daniel Jacobowitz
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=20020418103444.A21869@lucon.org \
--to=hjl@lucon.org \
--cc=gdb@sources.redhat.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