From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 18032@debbugs.gnu.org
Subject: bug#18032: Crash with etags
Date: Sun, 13 Oct 2019 03:24:48 +0200 [thread overview]
Message-ID: <87blulfndr.fsf@gnus.org> (raw)
In-Reply-To: <53C68133.6070103@cs.ucla.edu> (Paul Eggert's message of "Wed, 16 Jul 2014 06:42:11 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> [This bug report is taken from:
> http://lists.gnu.org/archive/html/emacs-devel/2014-07/msg00209.html
> I'm filing it here to give it a proper bug number and thread.
> Dr. Werner Fink <werner@suse.de> writes:]
[...]
> Reading symbols from /usr/bin/etags...Reading symbols from
> /usr/lib/debug/usr/bin/etags.debug...done.
> done.
> [New LWP 14768]
> Core was generated by `etags -a
> --regex=^\(ENTRY\|_GLOBAL\)(\([^)]*\)).* \2 /
> --regex=^SYSCALL_DEFINE['.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 __memcpy_sse2_unaligned () at
> ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37
> 37 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No
> such file or directory.
> (gdb) up
> #1 0x000000000040376c in memcpy (__len=90, __src=<optimized
> out>, __dest=0x18ea090) at /usr/include/bits/string3.h:51
> 51 return __builtin___memcpy_chk (__dest, __src, __len,
> __bos0 (__dest));
This was five years ago, and unfortunately this wasn't handled at the
time. But it's unlikely that we'll be making more progress here at this
point, so I'm closing this bug report. Please reopen if you're still
seeing these crashes in modern versions of Emacs.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-10-13 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 13:42 bug#18032: Crash with etags Paul Eggert
2019-10-13 1:24 ` Lars Ingebrigtsen [this message]
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=87blulfndr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=18032@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).