Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: Multiple breakpoints - few problems [MI commands, gdb6.7.50.20080221]
Date: Fri, 22 Feb 2008 13:22:00 -0000	[thread overview]
Message-ID: <fpmetg$4sp$1@ger.gmane.org> (raw)
In-Reply-To: <47BEB1E2.5070309@op.pl>

Bogdan Slusarczyk wrote:

> Hi, I have few problems using <MUTLIPLE> breakpoints with MI commands,

Well, MI does not currently explicitly support multiple locations
breakpoint -- that is you cannot see the individual locations or
operate on them.

> maybe you can help me.
> 1) to be sure: I can't delete sub-breakpoint, only disable it?

Correct.

> 2) sometimes gdb complains that can't set sub-breakpoint (Cannot insert
> breakpoint <whole number>. Error accessing memory address <address>.) 

This is not supposed to happen in the first place. Any ideas what
causes this error?

> 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?

You cannot, in MI. Can you maybe provide a minimal self-contained example
so that we can figure the cause of your original error (and maybe use it
as testcase for making the error message more precise).

- Volodya


> 
> Best regards,
> Bogdan



  reply	other threads:[~2008-02-22 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 12:24 Bogdan Slusarczyk
2008-02-22 13:22 ` Vladimir Prus [this message]
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='fpmetg$4sp$1@ger.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb@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