svn segfaults on Core 8.2 (but not on 7.2)

[mdv]

I've been using Core 7.2 (not Tiny Core) for several years without problem. Now, I'm upgrading to 8.2 (need the new kernel to be compatible with some new hardware) and am now getting segmentation faults when running svn.

To create the minimum reproducible environment, I have two VMware virtual machines running side by side, one with C7.2 mounted as an iso CD and the other with C8.2.1 (also tried with C8.2) to run this comparison.

To start, these are "virgin" installs booted straight from the .iso. Then run

Code: [Select]

tce-load -wi svn.tcz to get svn and its dependencies.

Then run a single svn  command

Code: [Select]

svn --username USER checkout https://SVNSERVICE.com/repo/path/to/code
On Core 7.2, everthing runs fine - repo is checked out and in a newly created directory.

On Core 8.2 and 8.2.1
After the same svn command above is initiated,

Code: [Select]

- warning "Error validating server certificate for 'https://SVNSERVICE.com:443'
- - the certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually.

• I manually accepted the certificate
• Then interactvely entered the password
• and got a Segmentation fault

The cert validation error is fixed by loading ca-certificates.tcz (don't know why this is different between 7.2 and 8.2) but it still segfaults

Also segfaults when running as root.

Both instances are running the same version of svn
svn version 1.7.5 (r1336830)
compiled Jul 27 2012, 17:10:15

The final few lines of the strace before the segfault are

Code: [Select]

open("/home/tc/TARGETDIR", Option...) =4
fstat64(4, {st_mode=S_IFDIRS|S_ISGIC|0755, st_size=60, ...}) = 0
getdents(4, /*3 entries */, 32768) = 48
--- SIGSEGV (Segmentation Fault) @ 0 (0) ---
+++ killed by SIGSEV +++
Segmentation fault
One thing that catches my eye is the fstat64 since I'm running on the (standard) Core i686 32 bit version (not x86_64)

The svn.tcz.info file shows that @juanito last updated this in 2012 to svn 1.7.5. Perhaps it's time to update to svn 1.8 or 1.9. I've also considered building a more recent version from source, but deferring to consider other options first.
 
At this point, I'm open to ideas of what to do next...

[curaga]

SVN is fairly easy to build IIRC, so do try a more recent version.

[Juanito]

Do you need the ca-certificates extension?

[Rich]

Hi mdv

To create the minimum reproducible environment, I have two VMware virtual machines running side by side, one with C7.2 mounted as an iso CD and the other with C8.2.1 (also tried with C8.2) to run this comparison.

Does the segfault also occur if you run  svn  on bare metal?

[mdv]

@curaga - I gave it a quick try to build svn from source, but found a second level of dependencies that I haven't have time to resolve yet.

@Juanito - When run without installing ca-certificates.tcz, svn will prompt me to manually accept the certificate offered by the svn server --- when ca-certificates.tcz is installed the manual prompt is no longer needed. In either case, svn still segfaults.

@Rich - I haven't tried it on bare metal, but will give that a try and report back.

Thanks to all for your feedback.

[Juanito]

updated svn posted