On Mon, Nov 26, 2001 at 06:48:42AM -0500, Roland McGrath wrote:
> > The crash came in file_name_lookup() presumably because there is no
> > working directory port yet.
>
> Don't presume, debug! There is no reason why file_name_lookup should ever
> produce a crash (unless given a bad string arg
> I am not so sure this should be considered a bug in libc, since by
> assuming the existence of the usual environment (including current
> directory) it can be faster the 99.99% of the time that that
> environment exists.
Such things are only true in specific, not generically.
Here there is
On Mon, Nov 26, 2001 at 06:48:42AM -0500, Roland McGrath wrote:
> > The crash came in file_name_lookup() presumably because there is no
> > working directory port yet.
>
> Don't presume, debug! There is no reason why file_name_lookup should ever
> produce a crash (unless given a bad string arg
> The crash came in file_name_lookup() presumably because there is no
> working directory port yet.
Don't presume, debug! There is no reason why file_name_lookup should ever
produce a crash (unless given a bad string argument), and if it does then
that is the bug (in libc).
_
Hi all,
I got a segfault where an informative diagnostic would have been
welcome. My mistake was to use "-T typed hd0s5" instead of "-T typed
device:hd0s5" in ext2fs.static's command line when bootstrapping.
The crash came in file_name_lookup() presumably because there is no
working directory p
