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#14080 - [sbackup] segfault
Attached to Project:
Arch Linux
Opened by Juanma Hernandez (juanmah) - Friday, 03 April 2009, 13:48 GMT
Last edited by Eric Belanger (Snowman) - Monday, 09 November 2009, 09:07 GMT
Opened by Juanma Hernandez (juanmah) - Friday, 03 April 2009, 13:48 GMT
Last edited by Eric Belanger (Snowman) - Monday, 09 November 2009, 09:07 GMT
|
DetailsWhen doing a backup by sbackupd or simple-backup-config I get a segfault:
sbackupd[22647]: segfault at 3979000 ip 00007f8da00f272b sp 00007fffa92467a8 error 4 in libc-2.9.so[7f8da0075000+14a000] In remote location, the subdirectory is created and only a file called base Notes: In i686 worked fine, same configuration. Version: extra/sbackup 0.10.5-1 Steps to reproduce: sudo /usr/sbin/sbackupd |
This task depends upon
Closed by Eric Belanger (Snowman)
Monday, 09 November 2009, 09:07 GMT
Reason for closing: Fixed
Additional comments about closing: works with new glibc
Monday, 09 November 2009, 09:07 GMT
Reason for closing: Fixed
Additional comments about closing: works with new glibc
Comment by Laszlo Papp (djszapi) -
Saturday, 07 November 2009, 18:02 GMT
Status ? if it exists maybe backtrace where the segfault occured ?
Comment by Juanma Hernandez (juanmah) -
Monday, 09 November 2009, 08:46 GMT
When glibc changed, it worked.