Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc][rfa:doc][rfa;testsuite] Add ``internal-warning''
Date: Thu, 12 Sep 2002 12:06:00 -0000	[thread overview]
Message-ID: <3D80E5CA.5000504@ges.redhat.com> (raw)
In-Reply-To: <3D5FF5F5.5080300@ges.redhat.com>

> Date: Thu, 15 Aug 2002 17:32:54 -0400
> From: Andrew Cagney <ac131313@ges.redhat.com>
> 
> This patch adds an internal_warning() function to GDB.  It's behavour is identical to internal_error() (quit? dump core?) only, at the end, it doesn't throw an error, instead returning to the caller.
> 
> 
>> I'd like gdb.texinfo to tell more about what GDB will print when this
>> command is invoked.  Perhaps just give an example.  ``behave as though
>> an internal error or warning is being reported'' doesn't sound
>> descriptive enough (it's not like every user is born with a built-in
>> knowledge of that behavior... ;-).

> 
> Makes sense, I'll do both.

How is this ...

<<<<

@kindex maint internal-error
@kindex maint internal-warning
@item maint internal-error
@itemx maint internal-warning
Cause @value{GDBN} to call the internal function @code{internal_error}
or @code{internal_warning} and hence behave as though an internal error
or internal warning has been detected.  In addition to reporting the
internal problem, these functions give the user the opportunity to 
either quit @value{GDBN} or create a core file of the current
@value{GDBN} session.

@smallexample
(gdb) @kbd{maint internal-error testing, 1, 2}
@dots{}/maint.c:121: internal-error: testing, 1, 2
A problem internal to GDB has been detected.  Further
debugging may prove unreliable.
Quit this debugging session? (y or n) @kbd{n}
Create a core file? (y or n) @kbd{n}
(gdb)
@end smallexample

Takes an optional parameter that is used as the text of the error or
warning message.

 >>>>

Andrew



  reply	other threads:[~2002-09-12 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 14:32 Andrew Cagney
2002-08-15 14:43 ` Fernando Nasser
2002-08-18 12:16 ` Eli Zaretskii
2002-08-18 12:31   ` Andrew Cagney
2002-09-12 12:06     ` Andrew Cagney [this message]
2002-09-19  4:32       ` Eli Zaretskii
2002-09-19  8:51         ` Andrew Cagney
2002-09-18 16:54 ` Andrew Cagney

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=3D80E5CA.5000504@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=eliz@is.elta.co.il \
    --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