Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7227 - emacs segfaults after system upgrade

Attached to Project: Arch Linux
Opened by Stathis K (Beket) - Monday, 21 May 2007, 18:55 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 22 May 2007, 17:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jürgen Hötzel (juergen)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After a system upgrade, emacs segfaults:

[stathis@archlinux ~]$ emacs
Segmentation fault

I got a backtrace and it goes like this:

Program received signal SIGSEGV, Segmentation fault.
0xb7c07cea in do_check_malloc_state () from /lib/libc.so.6
(gdb) bt
#0 0xb7c07cea in do_check_malloc_state () from /lib/libc.so.6
#1 0xb7c096cc in malloc_set_state () from /lib/libc.so.6
#2 0x080e1f8e in ?? ()
#3 0x08465858 in ?? ()
#4 0xb7bae1b0 in ?? () from /lib/libc.so.6
#5 0xbf9e7a2c in ?? ()
#6 0xb7cd1ff4 in ?? () from /lib/libc.so.6
#7 0xb7cd3120 in ?? () from /lib/libc.so.6
#8 0xbf9e7a2c in ?? ()
#9 0xbf9e74b4 in ?? ()
#10 0xb7c08e36 in ptmalloc_init () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
(gdb)

[stathis@archlinux ~]$ uname -a
Linux archlinux 2.6.21-ARCH #1 SMP PREEMPT Sun May 6 18:33:47 CEST 2007 i686 Intel(R) Pentium(R) 4 CPU 1.90GHz GenuineIntel GNU/Linux

I don't know if it helps but I upgraded to glibc 2.6

Thanks in advance
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 22 May 2007, 17:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  glibc 2.6-2 contains a patch for this problem.
Comment by Jan de Groot (JGC) - Tuesday, 22 May 2007, 11:01 GMT
Looks like a bug in glibc 2.6's malloc debugger. I've seen several post-2.6 commits in CVS for this, so I assume it's a glibc bug.
Comment by Stathis K (Beket) - Tuesday, 22 May 2007, 16:46 GMT
Thanx Jan for the response.
Let me know if there is anything I can do to help.

Loading...