From: Kevin Pouget <kevin.pouget@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Code cleanup - split print_stop_reason / question
Date: Wed, 27 Apr 2011 13:17:00 -0000 [thread overview]
Message-ID: <BANLkTikSc-o5jEmegpoE8n_76zDjQoG6Pw@mail.gmail.com> (raw)
In-Reply-To: <20110427130021.GA7103@host1.jankratochvil.net>
> This is not from me.
oh, sorry
at least, you're the last one who touched this line, right?
git blame gdb/infrun.c
...
8fc36186 (Jan Kratochvil 2010-09-04 14:27:43 +0000 5504)
ui_out_field_fmt (uiout, "exit-code", "0%o", (unsigned int)
exitstatus);
...
> 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:
ok, thanks
> AFAIK there was a tradition in UNIX to deal with program exit codes in octal.
> I do not know why.
ok, so if it's a tradition, let's perpetuate the tradition :)
--
Kevin
prev parent reply other threads:[~2011-04-27 13:17 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
2011-04-27 13:17 ` Kevin Pouget [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=BANLkTikSc-o5jEmegpoE8n_76zDjQoG6Pw@mail.gmail.com \
--to=kevin.pouget@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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