public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "michel.metzger at st dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13000] New: Return value with -batch is always 0 Date: Wed, 13 Jul 2011 20:44:00 -0000 [thread overview] Message-ID: <bug-13000-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13000 Summary: Return value with -batch is always 0 Product: gdb Version: 7.2 Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: michel.metzger@st.com Host: pc-linux-gnu Target: i686 The documentation states -batch has the following effect: "Exit with status 0 after processing all the command files specified with `-x' (and all commands from initialization files, if not inhibited with `-n'). Exit with nonzero status if an error occurs in executing the gdb commands in the command files." The following test demonstrates that it is in fact not the case: $ gdb -batch -x "gdb.script" with a file gdb.script containing the line: file toto (of course toto doesn't exist, to raise an error). The output is: gdb.script:1: Error in sourced command file: toto: No such file or directory. Displaying the exit status shows that is is in fact 0. $ echo $? 0 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-07-13 20:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-13 20:44 michel.metzger at st dot com [this message] 2014-06-25 12:23 ` [Bug gdb/13000] " tuben at lysator dot liu.se 2015-06-04 13:35 ` arma2ff0 at gmail dot com 2015-06-04 13:51 ` arma2ff0 at gmail dot com 2015-06-04 18:12 ` dje at google dot com 2015-06-05 11:50 ` arma2ff0 at gmail dot com 2023-12-31 12:23 ` ssbssa at sourceware dot org
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=bug-13000-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).