svk crashed with SIGSEGV in strchr()

Bug #320854 reported by Oumar Aziz OUATTARA
8
Affects Status Importance Assigned to Milestone
svk (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: svk

I wanted to mirror

https://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/linuxport/XBMC on a local repository different from ~/.svk/local

Got this error when syncing .

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/svk
InterpreterPath: /usr/bin/perl
NonfreeKernelModules: nvidia ath_hal
Package: svk 2.0.2-2ubuntu1.1
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/perl -w /usr/bin/svk sync /xbmc/upstream
ProcEnviron:
 SHELL=/bin/bash
 PATH=/media/sda5/opt/Maven/apache-maven-2.0.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
Signal: 11
SourcePackage: svk
StacktraceTop:
 strchr () from /lib/tls/i686/cmov/libc.so.6
 svn_fs__next_entry_name ()
 ?? () from /usr/lib/libsvn_fs_fs-1.so.1
 ?? () from /usr/lib/libsvn_fs_fs-1.so.1
 svn_fs_change_node_prop () from /usr/lib/libsvn_fs-1.so.1
Title: svk crashed with SIGSEGV in strchr()
Uname: Linux 2.6.27-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :
Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strchr () from /lib/tls/i686/cmov/libc.so.6
svn_fs__next_entry_name (next_p=0xbfde8ef4,
open_path (parent_path_p=0xbfde8f54, root=0x9e32ec0,
fs_change_node_prop (root=0x9e32ec0, path=0x0,
svn_fs_change_node_prop (root=0x9e32ec0, path=0x0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in svk:
importance: Undecided → Medium
Connor Imes (ckimes)
Changed in svk:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.