FS#27743 - [subversion] subversion (1.7.2-1) segfaults after glibc update
Attached to Project:
Arch Linux
Opened by Vladimir (_v_l) - Wednesday, 28 December 2011, 05:21 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 28 December 2011, 14:58 GMT
Opened by Vladimir (_v_l) - Wednesday, 28 December 2011, 05:21 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 28 December 2011, 14:58 GMT
|
Details
Description: subversion segfaults even on simple 'svn
--version' after upgrade to new glibc (ver. 2.15-1 [testing]
repo)
Additional info: * subversion: 1.7.2-1 * glibc: 2.15-1 Steps to reproduce: run in terminal $ svn --version I attach output from gdb (gdb svn > svn-version.log 2>&1) |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 28 December 2011, 14:58 GMT
Reason for closing: Duplicate
Additional comments about closing: Marking as duplicate for bug FS#27736
Traces are identical: apr_dso_load(), dlopen(), some glibc magic -> segfault
Wednesday, 28 December 2011, 14:58 GMT
Reason for closing: Duplicate
Additional comments about closing: Marking as duplicate for bug
Traces are identical: apr_dso_load(), dlopen(), some glibc magic -> segfault
P.S. I did:
$ sudo pacman -Su
$ svn --version
[segfault]
$ gdb svn > svn-version.log 2>&1
... run --version
... bt full
... quit
... y
I attach new 'svn-version.log' (just in case, if it helps).
1. Intel Core i5-2410M (notebook)
2. Intel Core2 Duo T6600 (notebook)
The other host I have is AMD Athlon 64 X2 Dual Core 5600+ but it doesn't use [testing] repo. On the other hand Archlinux i686 running under virtualbox, installed on Windows with AMD Athlon X4 processor, works fine.