On Thu, 19 Jun 2003 22:55:12 +0100
Richard Frith-Macdonald <richard@brainstorm.co.uk> wrote:
Please don't do that ... instead, track down the cause of the problem
and supply a fix, so other people don't have the problem in future.
However, if --disable-procfs gets rid of the symptom. it's probably
a
good idea to look at what information the operating system is
providing to the procfs code in NSProcessInfo.
1. there could be a bug in GNUsteps handling of procfs, which could
be
fixed.
2. there could be a bug in BSDs procfs, for which we could get
autoconf to enable a workaround (or disable procfs support if it is
horribly broken).
IIRC, I reported that /procfs problem a good 1 year a go (could be
even
more). GNUstep tries to access a couple of entries which simply do not
exist, like /procfs/self/exe (or sth like that) on BSD.