From: Michael Snyder <msnyder@cygnus.com>
To: John Hughes <john@Calva.COM>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: procfs.c thinks pid's can't be bigger than 99999
Date: Mon, 02 Jul 2001 11:56:00 -0000 [thread overview]
Message-ID: <3B40C3D0.1A96E1A7@cygnus.com> (raw)
In-Reply-To: <CDENKKMHIFMALMCCKPCFKEEJCAAA.john@Calva.COM>
John Hughes wrote:
>
> but on some systems, for example UnixWare NSC they
> can be quite a lot bigger.
>
> --- procfs.c.orig Tue May 15 02:03:36 2001
> +++ procfs.c Mon Jul 2 14:40:05 2001
> @@ -295,7 +295,7 @@
> # define AS_PROC_NAME_FMT "/proc/%d/as"
> # define MAP_PROC_NAME_FMT "/proc/%d/map"
> # define STATUS_PROC_NAME_FMT "/proc/%d/status"
> -# define MAX_PROC_NAME_SIZE sizeof("/proc/99999/lwp/8096/lstatus")
> +# define MAX_PROC_NAME_SIZE sizeof("/proc/1048576/lwp/8096/lstatus")
> # endif
> /* the name of the proc status struct depends on the implementation */
> typedef pstatus_t gdb_prstatus_t;
Well, actually, aren't we going to run into trouble if
pids are bigger than 16 bits? Or did Kevin Buettner's
recent changes take care of that?
Other than that, I have no problem with this change.
next prev parent reply other threads:[~2001-07-02 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 5:47 John Hughes
2001-07-02 11:56 ` Michael Snyder [this message]
2001-07-02 13:43 ` Kevin Buettner
2001-07-02 15:15 ` Michael Snyder
2001-07-03 12:28 ` Andrew Cagney
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=3B40C3D0.1A96E1A7@cygnus.com \
--to=msnyder@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=john@Calva.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