From: Tom Tromey <tom@tromey.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix /proc pathname sizes on Solaris
Date: Wed, 19 Sep 2018 12:58:00 -0000 [thread overview]
Message-ID: <87k1nhr6e7.fsf@tromey.com> (raw)
In-Reply-To: <yddlg80nrhk.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Mon, 17 Sep 2018 16:11:35 +0200")
>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
Rainer> - sprintf (pi->pathname, "/proc/%05d/lwp/%d", pid, tid);
Rainer> + sprintf (pi->pathname, "/proc/%d/lwp/%d", pid, tid);
FWIW gdb has xsnprintf which will check the length. Or I suppose it
wouldn't be hard to just change this to be a std::string and not worry
about lengths.
Tom
next prev parent reply other threads:[~2018-09-19 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 14:11 Rainer Orth
2018-09-17 18:35 ` Joel Brobecker
2018-09-17 19:27 ` Rainer Orth
2018-09-19 9:04 ` Rainer Orth
2018-09-19 13:21 ` Joel Brobecker
2018-09-19 12:58 ` Tom Tromey [this message]
2018-09-19 13:28 ` Rainer Orth
2018-09-19 15:16 ` Pedro Alves
2018-09-19 17:42 ` Rainer Orth
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=87k1nhr6e7.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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