Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH, gdb6.8] -break-list doesn't list multiple breakpoints
Date: Thu, 03 Apr 2008 06:44:00 -0000	[thread overview]
Message-ID: <ft1n6i$u5m$1@ger.gmane.org> (raw)
In-Reply-To: <18420.7112.284823.68348@kahikatea.snap.net.nz>

Nick Roberts wrote:

> Bogdan Slusarczyk writes:
>  > Hi everyone, I wrote my own patch for -break-list. I'm not sure that it
>  > meets all requirements mentioned in
>  > http://sourceware.org/ml/gdb-patches/2008-01/msg00251.html and previous
>  > discussions, but combination -break-list + multiple breakpoints is now
>  > usable for me. I'm not familiar with gdb test suit, so it's NOT tested
>  > at all (except few my own cases).
>  > 
>  > What does it do? Until now -break-list returned:
>  > ...
>  > 
>  > After my changes it returns additional list named 'locations' instead of
>  > second 'addr' field:
> 
> I don't think the second 'addr' field should be there, but I'm not sure that I
> really like this 'locations' field.  4.1, 4.2 etc are breakpoints and so I
> think they should be identified as such (using the bkptno field).

They are not really independent breakpoints. For example, condition is part of
the main breakpoint, and removing main breakpoint removes all locations, so
it's better to represent things this way.

- Volodya


  reply	other threads:[~2008-04-03  4:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 17:16 Bogdan Slusarczyk
2008-04-03  5:42 ` Nick Roberts
2008-04-03  6:44   ` Vladimir Prus [this message]
2008-04-03  9:21     ` Nick Roberts
2008-04-03 10:00       ` Vladimir Prus
2008-04-03 10:45         ` Nick Roberts
2008-04-03 10:49           ` Vladimir Prus
2008-04-03 11:28             ` Nick Roberts
2008-04-03 11:39               ` Vladimir Prus
2008-04-03 11:52               ` Bogdan Slusarczyk
2008-04-03 12:12                 ` Vladimir Prus
2008-04-03 12:48                   ` Bogdan Slusarczyk
2008-04-14 18:22 ` Daniel Jacobowitz
2008-04-15  8:35   ` Vladimir Prus
2008-04-15 20:13   ` Bogdan Slusarczyk

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='ft1n6i$u5m$1@ger.gmane.org' \
    --to=ghost@cs.msu.su \
    --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