Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: gdb 5.2 removes the conditional breakpoints
Date: Fri, 22 Mar 2002 10:45:00 -0000	[thread overview]
Message-ID: <20020322104516.A13317@lucon.org> (raw)
In-Reply-To: <3C9B76F5.6050809@cygnus.com>; from ac131313@cygnus.com on Fri, Mar 22, 2002 at 01:24:53PM -0500

On Fri, Mar 22, 2002 at 01:24:53PM -0500, Andrew Cagney wrote:
> > When I do
> > 
> > (gdb) b 100
> > (gdb) cond 1 i == 3
> > (gdb) r
> > (gdb) r
> > 
> > gdb 5.2 will remove the conditional breakpoints on Linux/x86 after I
> > restart the debug session. Am I the only one who sees it?
> 
> It would be very helpful if you could illustrate this problem by 
> submitting a real testcase.  That way people can run it and check 
> before/after effects on various platforms and GDB releases.
> 

It usually happened when I need it the most, like debugging glibc, gcc
and gdb :-). But it is hard to reproduce it when I want to. I will keep
an eye on it.


H.J.


  reply	other threads:[~2002-03-22 18:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22  9:50 H . J . Lu
2002-03-22 10:24 ` Andrew Cagney
2002-03-22 10:45   ` H . J . Lu [this message]
2002-03-22 10:27 ` Daniel Jacobowitz
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-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
2002-04-18 10:41         ` Daniel Jacobowitz
2002-04-18  9:42   ` H . J . Lu

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=20020322104516.A13317@lucon.org \
    --to=hjl@lucon.org \
    --cc=ac131313@cygnus.com \
    --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