From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 18586@debbugs.gnu.org
Subject: bug#18586: 24.4.50; "Not an in-range integer, float, or cons of integers" from x-focus-frame
Date: Thu, 2 Oct 2014 07:50:09 +0200 [thread overview]
Message-ID: <2C321CF0-E870-418D-A1D4-1CF0B93F781A@swipnet.se> (raw)
In-Reply-To: <542CDA6A.50406@cs.ucla.edu>
Hello.
2 okt 2014 kl. 06:54 skrev Paul Eggert <eggert@cs.ucla.edu>:
>> I guess the apropriate thing to do is to use cons_to_signed if the value fits in 32 signed bits, and cons_to_unsigned if it fits in 32 unsigned bits.
>
> There's already a function cons_to_x_long that does exactly that, and I'll look into a patch to use it. However, I suspect another bug is involved, as the reported value (0x385f739b4) does not fit in 32-bit unsigned long either, and I have a sneaking suspicion that it's garbage of some sort, i.e., that there's another bug at work here too.
If it does not fit in 32 bit unsigned, then it is indeed garbage. Unfortunately Time is unsigned long which might be 64 bit, but on the X protocol level it is 32 bit. So garbage may happen.
A watchpoint in gdb on dpyinfo->last_user_time by anyone who can reproduce this would find it.
Jan D.
next prev parent reply other threads:[~2014-10-02 5:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 14:04 bug#18586: 24.4.50; "Not an in-range integer, float, or cons of integers" from x-focus-frame Rupert Swarbrick
2014-09-30 4:03 ` Paul Eggert
2014-09-30 8:10 ` Leo Liu
2014-09-30 9:58 ` Leo Liu
2014-09-30 10:01 ` Rupert Swarbrick
2014-09-30 10:10 ` Leo Liu
2014-10-01 12:19 ` Rupert Swarbrick
2014-10-01 18:06 ` Jan Djärv
2014-09-30 13:24 ` Ted Zlatanov
2014-10-02 4:54 ` Paul Eggert
2014-10-02 5:50 ` Jan Djärv [this message]
2014-10-03 2:30 ` Paul Eggert
2014-10-03 8:22 ` Rupert Swarbrick
2014-10-04 21:27 ` Ted Zlatanov
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=2C321CF0-E870-418D-A1D4-1CF0B93F781A@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=18586@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).