From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: matthias.guedemann@googlemail.com, 21430@debbugs.gnu.org
Subject: bug#21430: 25.0.50; resizing window in exwm crashes emacs
Date: Tue, 15 Sep 2015 16:58:50 +0300 [thread overview]
Message-ID: <83613b942t.fsf@gnu.org> (raw)
In-Reply-To: <55F81A9B.1010400@gmx.at>
> Date: Tue, 15 Sep 2015 15:18:19 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 21430@debbugs.gnu.org
>
> > I think we still have one more bug that was uncovered by this report:
> > Fsignal aborted trying to report a wrong-type-arg error. That
> > shouldn't happen, and IMO we should continue looking into that, even
> > if the root cause which caused Fsignal to be invoked is gone.
>
> So what precisely are we trying to do? Make Fsignal abort I presume.
Yes.
> And apparently Matthias can't make it abort with a non-optimized build.
> So wouldn't this be a bug triggered by optimizations? Or a timing
> issue?
The optimizations factor should have been taken care of by building
without any options to configure.
The only other idea I have is return to the original binary which
started this thread, and look at values of some variables there using
the debugger.
next prev parent reply other threads:[~2015-09-15 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 7:57 bug#21430: 25.0.50; resizing window in exwm crashes emacs Matthias Güdemann
2015-09-07 16:20 ` Eli Zaretskii
2015-09-07 16:44 ` martin rudalics
2015-09-08 8:28 ` Matthias Güdemann
2015-09-08 9:09 ` martin rudalics
2015-09-08 9:25 ` Matthias Güdemann
2015-09-08 16:05 ` Eli Zaretskii
2015-09-08 16:49 ` Matthias Güdemann
2015-09-08 17:14 ` Eli Zaretskii
2015-09-09 8:22 ` Matthias Güdemann
2015-09-09 14:05 ` Eli Zaretskii
2015-09-15 12:39 ` Matthias Güdemann
2015-09-15 12:53 ` Eli Zaretskii
2015-09-15 13:18 ` martin rudalics
2015-09-15 13:58 ` Eli Zaretskii [this message]
2019-10-13 1:33 ` Lars Ingebrigtsen
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=83613b942t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21430@debbugs.gnu.org \
--cc=matthias.guedemann@googlemail.com \
--cc=rudalics@gmx.at \
/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.