[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-bugs] [bugs #12384] processor going mad

From: Amorphous
Subject: [Mldonkey-bugs] [bugs #12384] processor going mad
Date: Mon, 21 Mar 2005 07:56:51 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1

Follow-up Comment #7, bugs #12384 (project mldonkey):

you could compile mldonkey from the sources (30ab or 30-1) as follows
(replace "foo" with all the configure options you did use to compile):
./configure --enable-debug foo
make mlnet.byte

copy mlnet.byte to your mldonkey directory and cd into it
execute the debugger as follows and replace "/path/to/src/" with the path to
the directory src in the mldonkey sources:
ocamldebug $(find /path/to/src/ -name '.*' -prune -o -name 'gtk' -prune -o
-name 'gtk2' -prune -o -name 'applets' -prune -o -type d -printf '-I %p ')

then type the following in the debugger:
set checkpoints off

then wait until the problem occurs and do the following:
press ctrl-c and type:

then for each # greater than 0 type (and replace # with the number):
frame #

example for the last part:
(ocd) bt
#0  Pc : 6160  Test char 22
#1  Pc : 6160  Test char 22
#2  Pc : 6160  Test char 22
(ocd) frame 1
#1  Pc : 6160  Test char 22
2     <|b|>test ()
(ocd) frame 2
#2  Pc : 6160  Test char 22
2     <|b|>test ()

then copy and past all this (from when you ocamldebug started) into a file
and add this file to his bugreport.
i hope i can then make sense of it :) .


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]