Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: Thomas Fitzsimmons <fitzsim@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [WIP] pending breakpoint support
Date: Wed, 26 Nov 2003 20:02:00 -0000	[thread overview]
Message-ID: <3FC506D2.2020804@redhat.com> (raw)
In-Reply-To: <pan.2003.11.25.23.11.53.177553@redhat.com>

Thomas Fitzsimmons wrote:
> On Fri, 21 Nov 2003 17:46:43 -0500, J. Johnston wrote:
> 
> 
>>I have appended a patch to replace the previous hack.  I changed the
>>code so it supports conditionals and doesn't fail if you specify
>>source:line breakpoints. I also changed the mechanism to add a new flag
>>to the breakpoint struct called "pending".  As you will notice, this
>>adds a large number of checks because you can't just check for
>>enable_state == bp_enabled without also checking for the pending flag. 
>>I think that having two more enable states would have been simpler, but
>>I will let all of you decide.  With this change, you can enable/disable
>>the pending breakpoint and see any conditionals attached to it. Commands
>>should also work.
>>
> 
> 
> I've been using this patch since it was posted and it is very useful for
> both Mozilla and libgcj debugging.  One minor UI nit: I don't think I
> should be asked whether to make a breakpoint pending; I think the
> "pending" message is enough (or maybe the behaviour could be
> configurable).
>

IMO, the query should be the default.  If there is no query, every time you make 
a mistake, you would end up with an unwanted pending breakpoint.  Anybody, feel 
free to jump in with your comments.

Regarding the annoyance of having to answer many queries, this could be 
addressed in the future with a new setting, but that should be kept separate 
from the initial base implementation.

The query is not required for .gdbinit or mi.

-- Jeff J.

> In any case, even in its current early form, this patch is a huge
> improvement for shared-library debugging.
> 



  reply	other threads:[~2003-11-26 20:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19  1:03 J. Johnston
2003-11-19  6:03 ` Eli Zaretskii
2003-11-19 15:07 ` Daniel Jacobowitz
2003-11-19 23:32   ` J. Johnston
2003-11-19 23:52     ` Andrew Cagney
2003-11-21 22:46     ` J. Johnston
2003-11-25 23:20       ` Thomas Fitzsimmons
2003-11-26 20:02         ` J. Johnston [this message]
2003-11-26 20:30           ` Michael Snyder
2003-11-26 21:23             ` Thomas Fitzsimmons
2003-11-26 14:37       ` Andrew Cagney
2003-12-05  4:57       ` Daniel Jacobowitz
2003-11-19 19:47 ` Tom Tromey
     [not found] <1069259237.12557.ezmlm@sources.redhat.com>
2003-11-19 19:38 ` Jim Ingham

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=3FC506D2.2020804@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=fitzsim@redhat.com \
    --cc=gdb-patches@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