From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: More info on sporadic OS/X crash
Date: Wed, 28 Apr 2004 20:53:17 +0200 [thread overview]
Message-ID: <2719-Wed28Apr2004205317+0300-eliz@gnu.org> (raw)
In-Reply-To: <16527.37427.874467.884062@Ordesa.local> (piet@cs.uu.nl)
> From: "Piet van Oostrum" <piet@cs.uu.nl>
> 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?
next prev parent reply other threads:[~2004-04-28 18:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 23:15 More info on sporadic OS/X crash John Wiegley
2004-04-23 11:41 ` John Wiegley
2004-04-24 1:15 ` YAMAMOTO Mitsuharu
2004-04-25 17:49 ` Steven Tamm
2004-04-26 13:15 ` YAMAMOTO Mitsuharu
2004-04-26 16:27 ` Steven Tamm
2004-04-27 9:52 ` YAMAMOTO Mitsuharu
2004-04-27 15:24 ` Piet van Oostrum
2004-04-28 6:37 ` Eli Zaretskii
2004-04-28 11:14 ` Piet van Oostrum
2004-04-28 18:53 ` Eli Zaretskii [this message]
2004-04-29 12:10 ` Piet van Oostrum
2004-04-29 16:32 ` Kim F. Storm
2004-04-29 22:24 ` Steven Tamm
2004-04-29 22:25 ` Piet van Oostrum
2004-05-01 11:32 ` YAMAMOTO Mitsuharu
2004-04-26 18:08 ` John Wiegley
2004-04-27 9:59 ` YAMAMOTO Mitsuharu
2004-04-29 22:08 ` John Wiegley
2004-05-01 11:09 ` YAMAMOTO Mitsuharu
2004-05-07 1:24 ` John Wiegley
2004-05-10 6:02 ` John Wiegley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2719-Wed28Apr2004205317+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).