Daniel Wagner <[EMAIL PROTECTED]> writes:
> I have a question about the kmsg. Is the datastructer holding all kmsg is
> double linked circular list? I'm asking this, because I can't see it
> with gdb. For example following ikm_next and then comparing with
> the value of ikm_prev seems never to ma
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
> You may have to slowly track down what pages got
> used for what and how things got the way they are.
I have a question about the kmsg. Is the datastructer holding all kmsg is
double linked circular list? I'm asking this, because I can't see it
with gdb. For example following ikm_next and then
> 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).
_
Title: INTERSIGN
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Title: INTERSIGN
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
