From: John Baldwin <jhb@freebsd.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use a separate variable for the size passed to sysctl.
Date: Tue, 19 Jan 2016 19:36:00 -0000 [thread overview]
Message-ID: <1679587.CEfXXqWAZn@ralph.baldwin.cx> (raw)
In-Reply-To: <569E8C19.5060206@redhat.com>
On Tuesday, January 19, 2016 07:18:49 PM Pedro Alves wrote:
> OK with ...
>
> On 01/19/2016 06:24 PM, John Baldwin wrote:
> > --- a/gdb/ChangeLog
> > +++ b/gdb/ChangeLog
> > @@ -1,5 +1,10 @@
> > 2016-01-19 John Baldwin <jhb@FreeBSD.org>
> >
> > + * fbsd-tdep.c (fbsd_pid_to_exec_file): Use new "buflen" instead of
> > + "len" with sysctl.
>
> ... should be "fbsd-nat.c".
Err, yes. I also noticed after mailing that the 'len' variable is now
initialized unnecessarily (since it's value is always overwritten by the
call to readlink() after the #endif). Is it ok to push this modified
version:
--- a/gdb/fbsd-nat.c
+++ b/gdb/fbsd-nat.c
@@ -43,18 +43,20 @@
static char *
fbsd_pid_to_exec_file (struct target_ops *self, int pid)
{
- ssize_t len = PATH_MAX;
+ ssize_t len;
static char buf[PATH_MAX];
char name[PATH_MAX];
#ifdef KERN_PROC_PATHNAME
+ size_t buflen;
int mib[4];
mib[0] = CTL_KERN;
mib[1] = KERN_PROC;
mib[2] = KERN_PROC_PATHNAME;
mib[3] = pid;
- if (sysctl (mib, 4, buf, &len, NULL, 0) == 0)
+ buflen = sizeof buf;
+ if (sysctl (mib, 4, buf, &buflen, NULL, 0) == 0)
return buf;
#endif
--
John Baldwin
next prev parent reply other threads:[~2016-01-19 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 18:29 John Baldwin
2016-01-19 19:18 ` Pedro Alves
2016-01-19 19:36 ` John Baldwin [this message]
2016-01-19 22:53 ` Pedro Alves
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=1679587.CEfXXqWAZn@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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