Dear maintainer and reporter,
Based on my experimentation (though I use Ubuntu Linux, mixed releases
6.06/6.10) I suspect the segfault in recent versions of etags happens
whenever one uses the -R (--no-regex) option of etags. The option is
used together with the -r (--regex) option to control which tags etags
considers when building a tags file.
$ etags -R *.c
Segmentation fault (core dumped)
$ etags --no-regex *.c
Segmentation fault (core dumped)
The segfault happens no matter what file I try to run etags on, even
when I make up a filename.
$ etags -R Jason_Spiro_is_making_up_a_file_name_of_a_nonexistent_file
Segmentation fault (core dumped)
The segfault doesn't happen if I run etags -R without specifying a
filename though.
$ etags -R
etags: no input files specified.
Try `etags --help' for a complete list of options.
When I run etags without -R it works fine.
$ etags *.c
$ echo $?
0
My kernel:
$ uname -a
Linux dell 2.6.17-11-386 #2 Thu Feb 1 19:50:13 UTC 2007 i686 GNU/Linux
I use Ubuntu. Here is my libc version:
$ dpkg -s libc6 | grep ^Version
Version: 2.5-0ubuntu11
But I still wonder why this segfault happens. Can someone please
rebuild with debug symbols enabled (NOSTRIP,NOOPT should do it) and
get a backtrace? Just enter these three commands:
gdb --args etags -R *
run
backtrace full
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
