I cannot identify the exact place where things go wrong, so I have
uploaded the following files to http://people.debian.org/~jps/segfault/
RandomFunctions.cpp
amule
libcrypto++8-dbg_5.6.0-2_i386.deb
libcrypto++8_5.6.0-2_i386.deb
The amule binary is non-stripped and the interesting point is the
singleton in RandomFunctions.cpp, so you can set a break-point in the
get() method.
The exact shape of the singleton is my creation; the RandomFunctions.cpp
looks a little different in the original amule, but the segfault appears
in both implementations. The interesting thing is that the segfault
does not happen in the exact same place when the RandomFunction is
changed a bit. Therefore I suspect there could be some alignment
problems, also considering that the segfault does not happen on x64.
The -dbg package contains the debugging symbols for the crypto++
package.
Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
