[korg@archlinux ~]$ dangerdeep
Stack trace: (5 frames)
0x427c26 in at ??:0
0x422de5 in at ??:0
0x422ecb in at ??:0
0x7fd9ed64bc4d in __libc_start_main at ??:0
0x40a8e9 in at ??:0
[korg@archlinux ~]$
Did you simply alter the version numbers on those build files? (I must admit to near total ignorance of the arch build/packaging system, but they seem to still point to the 0.3.0 version)
Can you rebuild the package with debug symbols? (by altering the scons line to read scons debug=1)
The most probable cause is likely running the newer binary against older data,
the stacktrace also looks a little odd to my eyes, any chance you could paste the output of ldd /usr/bin/dangerdeep (or where-ever you installed the binary) ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How did you build/install dangerdeep ?
Hello,
I use this files to build dangerdeep package: http://repos.archlinux.org/wsvn/community/dangerdeep/trunk/
and this to build dangerdeep-data: http://repos.archlinux.org/wsvn/community/dangerdeep-data/trunk/
Hiya,
Did you simply alter the version numbers on those build files? (I must admit to near total ignorance of the arch build/packaging system, but they seem to still point to the 0.3.0 version)
Can you rebuild the package with debug symbols? (by altering the scons line to read scons debug=1)
The most probable cause is likely running the newer binary against older data,
the stacktrace also looks a little odd to my eyes, any chance you could paste the output of ldd /usr/bin/dangerdeep (or where-ever you installed the binary) ?
Ok, i will try with debug, and tell you about the result
Sorry, i still cant test this. Will wait package update in Arch Linux.
In case you are still wondering, try this:
./build/linux/dangerdeep --datadir data