[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: More info on sporadic OS/X crash
From: |
Eli Zaretskii |
Subject: |
Re: More info on sporadic OS/X crash |
Date: |
Wed, 28 Apr 2004 20:53:17 +0200 |
> From: "Piet van Oostrum" <address@hidden>
> Date: Wed, 28 Apr 2004 13:14:59 +0200
>
> (gdb) frame 1
> #1 0x0012eeac in sys_select (n=126, rfds=0x38e7e4, wfds=0x0, efds=0x0,
> timeout=0xbfffc770) at mac.c:2787
> 2787 return select(n, rfds, wfds, efds, timeout);
> (gdb) print *timeout
> $3 = {
> tv_sec = 0,
> tv_usec = 999996
> }
>
> So this looks normal.
Well, yes and no: how come it's 999996 microseconds instead of a full
second? That is, why don't you see this instead?
$3 = {
tv_sec = 1,
tv_usec = 0
}
This higher frame in the backtrace:
> #2 0x00119948 in wait_reading_process_input (time_limit=1, microsecs=0,
> read_kbd=3506604, do_display=0) at process.c:4311
seems to imply that wait_reading_process_input was called to wait for
1 second and 0 microseconds, so where from did the small inaccuracy
creep in?
- More info on sporadic OS/X crash, John Wiegley, 2004/04/15
- Re: More info on sporadic OS/X crash, John Wiegley, 2004/04/23
- Re: More info on sporadic OS/X crash, Piet van Oostrum, 2004/04/27
- Re: More info on sporadic OS/X crash, Eli Zaretskii, 2004/04/28
- Re: More info on sporadic OS/X crash, Piet van Oostrum, 2004/04/28
- Re: More info on sporadic OS/X crash,
Eli Zaretskii <=
- Re: More info on sporadic OS/X crash, Piet van Oostrum, 2004/04/29
- Re: More info on sporadic OS/X crash, Kim F. Storm, 2004/04/29
- Re: More info on sporadic OS/X crash, Piet van Oostrum, 2004/04/29
- Re: More info on sporadic OS/X crash, Steven Tamm, 2004/04/29
- Re: More info on sporadic OS/X crash, John Wiegley, 2004/04/26
- Re: More info on sporadic OS/X crash, YAMAMOTO Mitsuharu, 2004/04/27
- Re: More info on sporadic OS/X crash, John Wiegley, 2004/04/29