Message-ID:	<3A531017.CA005BC5@softhome.net>
Date:	Wed, 03 Jan 2001 12:42:15 +0100
From:	Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer:	Mozilla 4.76 [en] (Win98; U)
X-Accept-Language:	lt,en
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject:	Re: Stability of new long arg passing code?
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010103105453 DOT 1129N-100000 AT is>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> Is it certain that the library is the cause?  

No, it isn't - I'm just asking if somebody else has seen similar
things. 

> When did that start happening?  If it started recently, and if stock
> v2.03 libc doesn't have this problem, one possible cause might be the
> changes I committed for supporting CMDLINE on Windows.  

Probably (If the library turns out to be the cause, after all). The second 
most suspicious patch would be symlinks (because they touch child calling 
code too), but GCC did bootstrap with them earlier.

> One possible way to debug this is to add some debugging print-outs in
> the functions which issues this "Unrecognized option" message, and see
> what kind of data in there gets corrupted.

Thanks for tips; will investigate.

> What do you have for a shell when you see these problems?

Anything. bash 2.04, command.com from win98se, all kinds of file managers...

Laurynas

- Raw text -