From: Bogdan Slusarczyk <bodzio131@op.pl>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH, gdb6.8] -break-list doesn't list multiple breakpoints
Date: Thu, 03 Apr 2008 11:52:00 -0000 [thread overview]
Message-ID: <47F4C107.1020801@op.pl> (raw)
In-Reply-To: <18420.47850.169206.141581@kahikatea.snap.net.nz>
> I can imagine it might be useful to control the breakpoint locations
> individually but, in practice I've never needed multiple breakpoints yet.
I need it. Problem is that specific applications loads the same binaries
few times (see SystemC simulators), and multiple breakpoints are very
useful.
> However, if it's not useful then it's probably unlikely that anyone would
> try to do it in a frontend as you suggested earlier:
>
>
> Yes, but those are not a breakpoints, do it will do a disservice to the
> existing frontends. In particular, might find it very interesting
> experience to edit condition of one breakpoint, and having conditions on
> other breakpoints change. Likewise, changing any properly of location will
> not work.
I did changes for -break-list because I have situation when I have to
disable one of location, and I have to find such location. Location
behaves in different way as regular breakpoint, so I think it's not good
idea to mix this things. I treat locations rather as breakpoint
properties than regular breakpoints, but it's only my own opinion.
Regards,
Bogdan
next prev parent reply other threads:[~2008-04-03 11:36 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
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 [this message]
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=47F4C107.1020801@op.pl \
--to=bodzio131@op.pl \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=nickrob@snap.net.nz \
/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