From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: multiple breakpoint - is "Cannot insert breakpoint <..>. Error accessing memory address <..>" correct for location?
Date: Fri, 04 Apr 2008 16:01:00 -0000 [thread overview]
Message-ID: <ft5gov$fk9$1@ger.gmane.org> (raw)
In-Reply-To: <47F64410.5000907@op.pl>
Bogdan Slusarczyk wrote:
> Hi, I have situation when gdb cannot set multiple breakpoint at specific
> location. Suppose I have breakpoint with number 1, which has 3
> locations, but one of them cannot be set. Gdb returns: "Cannot insert
> breakpoint 1. Error accessing memory address 0x111111.".
Why does this error happen?
> I'm wondering
> that this message is ok, because it's not true that whole breakpoint
> cannot be set. Question is: will message "Cannot insert breakpoint 1.1"
> be ok? or something similar, maybe: "Cannot insert location 1.1"?
This (last) message of course is nicer. The question is how it should work
via MI? If -break-insert as the whole is deemed done, then user might never
know that some of the locations cannot be inserted.
- Volodya
prev parent reply other threads:[~2008-04-04 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 15:52 Bogdan Slusarczyk
2008-04-04 16:01 ` Vladimir Prus [this message]
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='ft5gov$fk9$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