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!
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!
FS#4144 - graveman segfaults with new glibc
Attached to Project:
Arch Linux
Opened by Björn Martensen (baze) - Saturday, 11 March 2006, 00:52 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 11 March 2006, 05:56 GMT
Opened by Björn Martensen (baze) - Saturday, 11 March 2006, 00:52 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 11 March 2006, 05:56 GMT
|
Detailsi use glibc 2.3.6-1 from testing and graveman 0.3.12.4-1 from extra.
i use en_US.utf8 by uncommenting en_US.UTF8 UTF8 in /etc/locale.gen. when i rescanned the devices and clicked "close" in graveman, it segfaulted. then i removed the configuration from ~/.config/graveman and now graveman segfaults on every hardware detection on its startup: *** glibc detected *** free(): invalid pointer: 0x080b2d98 *** |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 11 March 2006, 08:31 GMT
Reason for closing: Fixed
Additional comments about closing: next time file these in 4128
Fixing it now, another developer that frees g_object structures with g_free :(
Saturday, 11 March 2006, 08:31 GMT
Reason for closing: Fixed
Additional comments about closing: next time file these in 4128
Fixing it now, another developer that frees g_object structures with g_free :(
Comment by Tobias Powalowski (tpowa) -
Saturday, 11 March 2006, 05:56 GMT
probably more glib2 related then glibc.