Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: <Paul_Koning@Dell.com>
To: <daniel.gutson@tallertechnologies.com>
Cc: <gdb@sourceware.org>
Subject: Re: specifying gdb's exit code
Date: Thu, 17 Apr 2014 19:08:00 -0000	[thread overview]
Message-ID: <8409270A-85C4-43D0-9D4D-5CB676B9DF31@dell.com> (raw)
In-Reply-To: <CAF5HaEVTZAxc0FNR9GnGNKJqxGSrbQaTfZ7ZRMoueTg6jQyL8A@mail.gmail.com>

You can do this using Python scripting:

(gdb) python import sys; sys.exit(123)

	paul

On Apr 17, 2014, at 2:43 PM, Daniel Gutson <daniel.gutson@tallertechnologies.com> wrote:

> Hi,
> 
>   Due to a specific need, I was thinking of a way to specify (e.g.
> from a script) the gdb exit status,
> specially in terms of the $_exitcode.
> 
> AFAIK, this is not currently possible since gdb returns only about the
> finalization execution status
> of the inf. I understand that these could be messed, specially when in
> --batch mode, but it should be
> responsibility of the developer to specify an exit code different to
> those gdb may return, and also
> responsibility of the invoking program to make such distinction.
> 
> The options I can think about are:
>  - set a convenience var, such as $_gdbexitcode
>  - set gdb-exit-code [n]
>  - add an optional argument to the 'quit' command  (so "quit
> $_exitcode" is available)
> 
> Ideas?
> 
> Thanks!
> 
>    Daniel.
> 
> -- 
> 
> Daniel F. Gutson
> Chief Engineering Officer, SPD
> 
> 
> San Lorenzo 47, 3rd Floor, Office 5
> 
> Córdoba, Argentina
> 
> 
> Phone: +54 351 4217888 / +54 351 4218211
> 
> Skype: dgutson


  reply	other threads:[~2014-04-17 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 18:48 Daniel Gutson
2014-04-17 19:08 ` Paul_Koning [this message]
2014-04-17 19:58 ` Daniel Gutson
2014-04-17 21:35   ` Doug Evans
2014-04-17 21:52     ` Daniel Gutson
2014-04-18  8:20       ` Daniel Gutson
2014-04-22 12:55         ` Daniel Gutson
2014-04-22 12:59 ` Andrew Stubbs
2014-04-22 13:06   ` Daniel Gutson

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=8409270A-85C4-43D0-9D4D-5CB676B9DF31@dell.com \
    --to=paul_koning@dell.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --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