GNU bug report logs - #14982
24.3; core dump on NetBSD in graphical mode on files in cvs

Previous Next

Full log

Message #38 received at 14982 <at> debbugs.gnu.org (full text, mbox):

From: Thomas Klausner <tk <at> giga.or.at>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 14982 <at> debbugs.gnu.org
Subject: Re: 24.3; core dump on NetBSD in graphical mode on files in cvs
Date: Sat, 7 Sep 2013 00:16:16 +0200

On Thu, Sep 05, 2013 at 06:07:01AM -0700, Paul Eggert wrote:
> Sorry, I've never used NetBSD so I don't have
> any ideas other than "run GDB and tear your
> hair out".

Some minimal progress:
# emacs creating.xml 
Fatal error 11: Segmentation fault
Backtrace:
0x4ea7d6 <XSetWMNormalHints+0x21a0f> at emacs
0x4d04c2 <XSetWMNormalHints+0x76fb> at emacs
0x4e952e <XSetWMNormalHints+0x20767> at emacs
0x4e95de <XSetWMNormalHints+0x20817> at emacs
zsh: segmentation fault (core dumped)  emacs creating.xml
# ulimit -a
-t: cpu time (seconds)              unlimited
-f: file size (blocks)              unlimited
-d: data seg size (kbytes)          262144
-s: stack size (kbytes)             4096
-c: core file size (blocks)         unlimited
-m: resident set size (kbytes)      32512204
-l: locked-in-memory size (kbytes)  10837401
-u: processes                       160
-n: file descriptors                128
-b: socket buffer size (bytes)      unlimited
-v: virtual memory size (kbytes)    unlimited
-r: threads                         160
# ulimit -s 20000
# emacs creating.xml
(works)

So there seems to be some big object on the stack.

What are your stack size settings?
Can you reproduce this segfault by reducing your stack size?

Suggestions where to look?

Thanks,
 Thomas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.