From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Code cleanup - split print_stop_reason / question
Date: Wed, 27 Apr 2011 13:01:00 -0000 [thread overview]
Message-ID: <20110427130021.GA7103@host1.jankratochvil.net> (raw)
In-Reply-To: <BANLkTin70pF0swcBvPZ3ftSmbrrccOUzcw@mail.gmail.com>
On Wed, 27 Apr 2011 13:27:38 +0200, Kevin Pouget wrote:
> I had a little question regarding Jan's patch below,
> do you remember why you print the `exitstatus' in octal?
This is not from me. When you check the history (I use git annotate file,
git annotate file REVISION^, git annotate file PREVREVISION^ and so on) you
will find that line of code comes from:
commit 14558c99c9b3adcfd7ab7934392a7b958337a015
Author: Jason Molenda <jsm@bugshack.cygnus.com>
Date: Thu Feb 3 04:14:45 2000 +0000
import gdb-2000-02-02 snapshot
So there is no further history and the line's original author is unknown.
AFAIK there was a tradition in UNIX to deal with program exit codes in octal.
I do not know why.
Thanks,
Jan
next prev parent reply other threads:[~2011-04-27 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTin70pF0swcBvPZ3ftSmbrrccOUzcw@mail.gmail.com>
2011-04-27 11:34 ` Kevin Pouget
2011-04-27 13:01 ` Jan Kratochvil [this message]
2011-04-27 13:17 ` Kevin Pouget
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=20110427130021.GA7103@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=kevin.pouget@gmail.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