From: Francesco Potorti` <pot@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: "make tags" segfaults
Date: 03 Sep 2002 13:11:17 +0200 [thread overview]
Message-ID: <87wuq38h0q.fsf@pot.cnuce.cnr.it> (raw)
In-Reply-To: <vafr8gceh30.fsf@lucy.cs.uni-dortmund.de>
(gdb) run --include=TAGS-LISP --include=../lwlib/TAGS --regex='/[ ]*DEFVAR_[A-Z_ (]+"\([^"]+\)"/' /home-local/grossjoh/work/gnu/emacs/src/[xyzXYZ]*.[hc] /home-local/grossjoh/work/gnu/emacs/src/[a-wA-W]*.[hc]
Starting program: /home-local/grossjoh/work/gnu/emacs/lib-src/etags --include=TAGS-LISP --include=../lwlib/TAGS --regex='/[ ]*DEFVAR_[A-Z_ (]+"\([^"]+\)"/' /home-local/grossjoh/work/gnu/emacs/src/[xyzXYZ]*.[hc] /home-local/grossjoh/work/gnu/emacs/src/[a-wA-W]*.[hc]
Program received signal SIGSEGV, Segmentation fault.
0x4008d219 in malloc () from /lib/libc.so.6
(gdb) w
Ambiguous command "w": watch, wh, whatis, where, while, while-stepping, winheight, ws.
(gdb) where
#0 0x4008d219 in malloc () from /lib/libc.so.6
#1 0x4008d074 in malloc () from /lib/libc.so.6
#2 0x0805042e in xmalloc (size=20)
at /home-local/grossjoh/work/gnu/emacs/lib-src/etags.c:6602
This should mean that there has been memory corruption in the malloc
structures :-(
I cannot reproduce the bug, and none of my tests fail. Moreover, I
cannot easily deduce where the memory corruption happens. When
developing, I usually instrument etags with a small checkmalloc library.
If you can use a malloc checking library yourself, please try to do so
and report the results to me.
Else, I can send you the two source files needed for that library and
the small modifications to the Makefile for building and running etags
with malloc instrumentation.
next prev parent reply other threads:[~2002-09-03 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 12:01 "make tags" segfaults Kai Großjohann
2002-09-03 11:11 ` Francesco Potorti` [this message]
2002-09-03 11:57 ` Kai Großjohann
2002-09-03 13:41 ` Francesco Potorti`
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=87wuq38h0q.fsf@pot.cnuce.cnr.it \
--to=pot@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 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.