From: "Jan D." <jan.h.d@swipnet.se>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: SEGV in xmenu.c digest_single_submenu
Date: Tue, 11 Apr 2006 10:34:46 +0200 [thread overview]
Message-ID: <443B6A26.2090006@swipnet.se> (raw)
In-Reply-To: <m28xqc4jch.fsf@kenny.sha-bang.de>
Sascha Wilde wrote:
> Richard Stallman <rms@gnu.org> wrote:
>
>> Luckily I was able to reproduce the crash after starting emacs from
>> gdb.
>>
>> Can you tell us a precise recipe for reproducing it?
>
> I'm working on it. I can reproduce the problem, but not with emacs -Q
> (only with loaded .emacs).
>
> What I do is
> - start emacs
> - C-x 5 f /PATH/TO/EMACS/src/xmenu.c
> => SIGSEGV
>
> GDB:
> Program received signal SIGSEGV, Segmentation fault.
> 0x08086f5c in digest_single_submenu (start=3803, end=4928,
> top_level_items=0)
> at xmenu.c:1850
> 1850 save_wv->contents = wv;
> (gdb) p save_wv
> $22 = (widget_value *) 0x0
>
>
> As you can see, the problem is at a little bit altered location,
> compared to my last report. I can reproduce _this_ problem absolutely
> reliable, but only with .emacs loaded.
>
> I'm not sure what to look for in .emacs that might cause the
> problem -- but in any case I would think that lisp code shouldn't
> cause a SEGV in any case.
This is the same as the thread "Problem #18" talks about, save_wv being
dereferenced while it is NULL. Do our .emacs load any c-mode customizations,
such as special menu entries? Or some minor mode that adds a menu for C-files?
Jan D.
next prev parent reply other threads:[~2006-04-11 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 7:44 SEGV in xmenu.c digest_single_submenu Sascha Wilde
2006-04-10 18:25 ` Richard Stallman
2006-04-11 8:17 ` Sascha Wilde
2006-04-11 8:34 ` Jan D. [this message]
2006-04-11 11:12 ` Sascha Wilde
2006-04-11 14:20 ` Sascha Wilde
2006-04-14 19:37 ` Sascha Wilde
2006-04-17 12:09 ` Jan Djärv
2006-04-20 7:44 ` Sascha Wilde
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=443B6A26.2090006@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=rms@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).