Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Konstantin Karganov <kostik@ispras.ru>
To: gdb@sources.redhat.com
Subject: Incorrect breakpoint diagnostics in MI
Date: Thu, 14 Jul 2005 15:15:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0507141852300.29233-100000@ispserv.ispras.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0507141801580.29233-100000@ispserv.ispras.ru>

Hello.

Playing with MI breakpoint commands I found the following thing:
Only "-break-after" and "-break-condition" correctly report the error if 
the breakpoint doesn't exist. While other commands report "^done".

(gdb)
-break-after 123 123
&"No breakpoint number 123.\n"
^error,msg="No breakpoint number 123."
(gdb)
-break-enable 123
~"No breakpoint number 123.\n"
^done
(gdb)
-break-disable 123
~"No breakpoint number 123.\n"
^done
(gdb)
-break-delete 123
~"No breakpoint number 123.\n"
^done

The diagnostics goes to console output, that is possibly not visible to FE 
user and the result itself is "ok".

Is it a bug?

Best reagards,
Konstantin.



      parent reply	other threads:[~2005-07-14 15:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 16:21 Thread backtrace termination Jonathan Larmour
2005-07-11 16:23 ` Daniel Jacobowitz
2005-07-11 17:52   ` Jonathan Larmour
2005-07-11 18:19     ` Daniel Jacobowitz
2005-07-12 18:32       ` Jonathan Larmour
2005-07-13 10:35         ` Steven Johnson
2005-07-13 12:53           ` GDB is stepping past main() Konstantin Karganov
2005-07-13 13:05             ` Daniel Jacobowitz
2005-07-13 13:31               ` Konstantin Karganov
2005-07-13 13:39                 ` Nathan J. Williams
2005-07-13 13:47                   ` Konstantin Karganov
2005-07-13 13:50                     ` Dave Korn
2005-07-13 13:46                 ` Daniel Jacobowitz
2005-07-13 13:57                   ` Konstantin Karganov
2005-07-14 14:27                   ` MI *stopped reason Konstantin Karganov
2005-07-14 14:40                     ` Bob Rossi
2005-07-14 15:15                     ` Konstantin Karganov [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=Pine.LNX.4.44.0507141852300.29233-100000@ispserv.ispras.ru \
    --to=kostik@ispras.ru \
    --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