I don't think there is an easily reproducible sequence to do this.
This is how I normally start amule, first I launch amule, then once I see it is running click connect, and connect to both an ed2k server and the kad network, then I check transfers by sorting by sources, then minimize amule to the tray. after that it seems to vary what I do and how long it takes to crash...
I installed valgrind using yast's rpm and tried using the following command slightly modified from that valgrind site, due to not having the same switches:
valgrind -v --tool=memcheck --leak-check=yes --db-attach=yes --num-callers=10 --gen-suppressions=yes /usr/local/bin/amule --enable-stdin
How do I pass it the --even-if-lfroen-complains-this-will-stay switch?
when it crashes using this will it dump a backtrace too? or is there something specific I should look for?
when I ran the above command I got the following at the end:
==9179== LEAK SUMMARY:
==9179== definitely lost: 2,142 bytes in 3 blocks.
==9179== possibly lost: 19,880 bytes in 35 blocks.
==9179== still reachable: 103,811 bytes in 1,401 blocks.
==9179== suppressed: 0 bytes in 0 blocks.
==9179== Reachable blocks (those to which a pointer was found) are not shown.
==9179== To see them, rerun with: --show-reachable=yes
--9179-- memcheck: sanity checks: 83 cheap, 4 expensive
--9179-- memcheck: auxmaps: 0 auxmap entries (0k, 0M) in use
--9179-- memcheck: auxmaps: 0 searches, 0 comparisons
--9179-- memcheck: SMs: n_issued = 65 (1040k, 1M)
--9179-- memcheck: SMs: n_deissued = 0 (0k, 0M)
--9179-- memcheck: SMs: max_noaccess = 65535 (1048560k, 1023M)
--9179-- memcheck: SMs: max_undefined = 0 (0k, 0M)
--9179-- memcheck: SMs: max_defined = 388 (6208k, 6M)
--9179-- memcheck: SMs: max_non_DSM = 65 (1040k, 1M)
--9179-- memcheck: max sec V bit nodes: 11 (0k, 0M)
--9179-- memcheck: set_sec_vbits8 calls: 33 (new: 11, updates: 22)
--9179-- memcheck: max shadow mem size: 1344k, 1M
--9179-- translate: fast SP updates identified: 48,821 ( 90.5%)
--9179-- translate: generic_known SP updates identified: 2,970 ( 5.5%)
--9179-- translate: generic_unknown SP updates identified: 2,120 ( 3.9%)
--9179-- tt/tc: 70,969 tt lookups requiring 95,829 probes
--9179-- tt/tc: 70,969 fast-cache updates, 5 flushes
--9179-- transtab: new 28,090 (706,935 -> 10,319,143; ratio 145:10) [0 scs]
--9179-- transtab: dumped 0 (0 -> ??)
--9179-- transtab: discarded 131 (2,476 -> ??)
--9179-- scheduler: 8,353,084 jumps (bb entries).
--9179-- scheduler: 83/51,827 major/minor sched events.
--9179-- sanity: 84 cheap, 4 expensive checks.
--9179-- exectx: 30,011 lists, 4,701 contexts (avg 0 per list)
--9179-- exectx: 8,350 searches, 4,050 full compares (485 per 1000)
--9179-- exectx: 21,865 cmp2, 4 cmp4, 0 cmpAll
not sure if that helps...
