From: Bogdan Slusarczyk <bodzio131@op.pl>
To: gdb@sourceware.org
Subject: Multiple breakpoints - few problems [MI commands, gdb6.7.50.20080221]
Date: Fri, 22 Feb 2008 12:24:00 -0000 [thread overview]
Message-ID: <47BEB1E2.5070309@op.pl> (raw)
Hi, I have few problems using <MUTLIPLE> breakpoints with MI commands,
maybe you can help me.
1) to be sure: I can't delete sub-breakpoint, only disable it?
2) sometimes gdb complains that can't set sub-breakpoint (Cannot insert
breakpoint <whole number>. Error accessing memory address <address>.) I
want to disable such sub-breakpoint, but I can't because:
a) <whole number> it's not sub-breakpoint id
b) I could use <address> to find sub-breakpoint, but it's impossible
because -break-list (or -break-info <whole number>) doesn't return any
information about sub-breakpoints.
Is it a bug or I missed something? How can I list sub-breakpoints?
Best regards,
Bogdan
next reply other threads:[~2008-02-22 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 12:24 Bogdan Slusarczyk [this message]
2008-02-22 13:22 ` Vladimir Prus
2008-02-23 12:52 ` Bogdan Slusarczyk
2008-02-23 16:03 ` Vladimir Prus
2008-02-25 12:08 ` 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=47BEB1E2.5070309@op.pl \
--to=bodzio131@op.pl \
--cc=gdb@sourceware.org \
/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