From: Alain Schneble <a.s@realize.ch>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24614@debbugs.gnu.org
Subject: bug#24614: 25.1.50; Exception after moving mouse over over a different window
Date: Tue, 4 Oct 2016 19:24:34 +0200 [thread overview]
Message-ID: <86vax82fjh.fsf@realize.ch> (raw)
In-Reply-To: <83fuocm48z.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 04 Oct 2016 20:08:12 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> What about
>
> (gdb) p *glyph
>
(gdb) p *glyph
Cannot access memory at address 0x10c46fd0
(Not a valid excuse for having missed that one, but sorry, I was in a
hurry. I had to leave the train.)
>> > Btw, how come the call to get_window_cursor_type is shown with its
>> > argument in reverse order? In the backtrace:
>>
>> I have no clue... Could optimization reorder the arguments?
>
> Maybe the function was inlined. Or maybe it's a GDB bug.
Aha.
>> > Something really weird went on in that frame #10...
>>
>> Should I have fear of something now? ;)
>
> Fear of a crash, of course.
I'll resist.
> If this happens again, I suggest to build an unoptimized binary and
> see if the problem can be reproduced there.
Ok, I'll watch out and will try to catch it with an unoptimized build if
that happens again.
Thanks,
Alain
next prev parent reply other threads:[~2016-10-04 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 14:53 bug#24614: 25.1.50; Exception after moving mouse over over a different window Alain Schneble
2016-10-04 15:44 ` Eli Zaretskii
2016-10-04 15:54 ` Alain Schneble
2016-10-04 16:19 ` Eli Zaretskii
2016-10-04 16:25 ` Alain Schneble
2016-10-04 17:08 ` Eli Zaretskii
2016-10-04 17:24 ` Alain Schneble [this message]
2016-10-04 17:41 ` Eli Zaretskii
2016-10-04 18:06 ` Alain Schneble
2016-10-04 19:15 ` Eli Zaretskii
2016-10-04 20:08 ` Alain Schneble
2016-10-04 16:06 ` Alain Schneble
2016-10-04 16:31 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86vax82fjh.fsf@realize.ch \
--to=a.s@realize.ch \
--cc=24614@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.