From: "Alfred M. Szmidt" <ams@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs from head segfaults when run with -nw
Date: Thu, 08 Apr 2010 16:03:55 -0400 [thread overview]
Message-ID: <E1NzxxD-0006pq-5C@fencepost.gnu.org> (raw)
In-Reply-To: <8339z8x8oq.fsf@gnu.org> (message from Eli Zaretskii on Wed, 07 Apr 2010 06:06:45 +0300)
> (gdb) xbacktrace
> "where-is-internal" (0xbfffdd64)
> "tool-bar-local-item-from-menu" (0xbfffe034)
> "apply" (0xbfffe164)
> "tool-bar-add-item-from-menu" (0xbfffe424)
> "tool-bar-setup" (0xbfffe6e4)
> "tool-bar-mode" (0xbfffe994)
> "command-line" (0xbfffec54)
> "normal-top-level" (0xbfffee70)
??? How come tool-bar functions are called in a non-GUI session?
Non-GUI sessions could have tool-bar support, so it isn't harmful to
call tool-bar-mode; very much like scroll-bar-mode is also called for
non-GUI sessions.
next prev parent reply other threads:[~2010-04-08 20:03 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 19:02 emacs from head segfaults when run with -nw Alfred M. Szmidt
2010-04-02 20:49 ` Dan Nicolaescu
2010-04-02 23:07 ` Juri Linkov
2010-04-02 23:48 ` Dan Nicolaescu
2010-04-03 10:42 ` Alfred M. Szmidt
2010-04-03 19:19 ` Dan Nicolaescu
2010-04-03 22:12 ` Juri Linkov
2010-04-03 23:56 ` Ken Hori
2010-04-04 11:06 ` Juri Linkov
2010-04-04 8:10 ` Jan Djärv
2010-04-05 17:22 ` Dan Nicolaescu
2010-04-14 15:05 ` Randal L. Schwartz
2010-04-18 2:35 ` Randal L. Schwartz
2010-04-18 3:05 ` Randal L. Schwartz
2010-04-05 9:04 ` Eli Zaretskii
2010-04-05 13:34 ` Alfred M. Szmidt
2010-04-05 14:06 ` Eli Zaretskii
2010-04-05 15:03 ` Alfred M. Szmidt
2010-04-05 15:24 ` Eli Zaretskii
2010-04-06 21:08 ` Alfred M. Szmidt
2010-04-07 3:06 ` Eli Zaretskii
2010-04-08 20:03 ` Alfred M. Szmidt [this message]
2010-04-05 16:49 ` Eli Zaretskii
2010-04-05 16:59 ` Juri Linkov
2010-04-05 21:39 ` Eli Zaretskii
2010-04-06 0:41 ` Stefan Monnier
2010-04-05 13:52 ` Stefan Monnier
2010-04-05 14:17 ` Eli Zaretskii
2010-04-05 20:00 ` Sean Sieger
2010-04-05 21:49 ` Eli Zaretskii
2010-04-06 18:49 ` Andreas Schwab
2010-04-07 3:25 ` Eli Zaretskii
2010-04-07 3:57 ` Stefan Monnier
2010-04-07 5:35 ` Eli Zaretskii
2010-04-07 11:11 ` Juanma Barranquero
2010-04-09 11:10 ` Eli Zaretskii
2010-04-10 1:25 ` Stefan Monnier
2010-04-05 14:11 ` Chong Yidong
2010-04-05 14:19 ` Eli Zaretskii
2010-04-16 14:18 ` Juanma Barranquero
2010-04-16 21:06 ` Eli Zaretskii
2010-04-16 23:18 ` Juanma Barranquero
2010-04-17 7:55 ` Eli Zaretskii
2010-04-17 16:19 ` Juanma Barranquero
2010-04-17 16:37 ` Eli Zaretskii
2010-04-17 19:12 ` Juanma Barranquero
2010-04-17 19:18 ` Eli Zaretskii
2010-04-17 19:20 ` Juanma Barranquero
2010-04-17 21:02 ` Eli Zaretskii
2010-04-16 8:26 ` Sascha Wilde
2010-04-16 21:01 ` Eli Zaretskii
2010-04-17 10:28 ` Sascha Wilde
2010-04-17 12:39 ` Eli Zaretskii
2010-04-17 18:49 ` Sascha Wilde
2010-04-19 12:31 ` Eli Zaretskii
2010-04-20 10:30 ` Sascha Wilde
2010-04-20 12:03 ` 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
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=E1NzxxD-0006pq-5C@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=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).