mldonkey-bugs
[Top][All Lists]
Advanced

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

[Mldonkey-bugs] [Bug #975] Bus Error under Jaguar GM


From: nobody
Subject: [Mldonkey-bugs] [Bug #975] Bus Error under Jaguar GM
Date: Sun, 18 Aug 2002 20:52:33 -0400

=================== BUG #975: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=975&group_id=1409

Changes by: Anonymous user        Date: 2002-Aug-18 20:52

------------------ Additional Follow-up Comments ----------------------------
CVS head compiles "out of the box" on Shaguar preview (10.2),
but still reliably dumps core from 1.5 to 15 minutes after mldonkey
starts, with the same problem as noted earlier in this bug.

Also, "quit" at a telnet connection to mldonkey (port 4000),
or quitting the GUI, causes an immediate bus error, unfortunately
without a useful traceback or core dump.

Would a ktrace help?  Preview version allows that, but the output tends
to be B-I-G.




=================== BUG #975: FULL BUG SNAPSHOT ===================


Submitted by: None                      Project: mldonkey, a free e-Donkey 
client
Submitted on: 2002-Aug-09 15:22
Category:  None                         Severity:  5 - Major                    
Bug Group:  None                        Resolution:  None                       
Assigned to:  None                      Status:  Open                           

Summary:  Bus Error under Jaguar GM

Original Submission:  mldonkey seems to run all right for a couple minutes 
under Mac OS X 10.2 Jaguar 6C115 (GM), but then reports a bus error and quits.

Follow-up Comments
*******************

-------------------------------------------------------
Date: 2002-Aug-18 20:52             By: None
CVS head compiles "out of the box" on Shaguar preview (10.2),
but still reliably dumps core from 1.5 to 15 minutes after mldonkey
starts, with the same problem as noted earlier in this bug.

Also, "quit" at a telnet connection to mldonkey (port 4000),
or quitting the GUI, causes an immediate bus error, unfortunately
without a useful traceback or core dump.

Would a ktrace help?  Preview version allows that, but the output tends
to be B-I-G.


-------------------------------------------------------
Date: 2002-Aug-18 12:08             By: None
possibly useful informatin from crash reports 
(~/Library/Logs/mldonkey.crash.log) for three SIGBUS deaths where partial state
was available:

Thread 0 Crashed:
 #0   0x000c1470 in LittleEndian__get_int32_32_95
 #1   0x0004a830 in Donkey__fun_1079

Thread 0 Crashed:
 #0   0x0000a734 in DriverControlers__user_reader_634
 #1   0x00105900 in caml_c_call

Thread 0 Crashed:
 #0   0x0000a734 in DriverControlers__user_reader_634
 #1   0x00105900 in caml_c_call



-------------------------------------------------------
Date: 2002-Aug-17 16:56             By: None
The CVS (trunk, 2002 08 17) mldonkey 1.99 gives a bus error 
immediately after the following sequence (with verbose=true)

[FOUND FILE][FOUND FILE][FOUND FILE][FOUND FILE][FOUND 
FILE][QUEUED][FREE][NEXT]Bus error

which of course points to donkey/donkeyOneFile.ml as location of
the culprit code...   This is reliably and trivially repeatable.

-------------------------------------------------------
Date: 2002-Aug-16 15:23             By: None
I'm trying to recompile with Jaguar Developer Tools (We got Jaguar in at the 
store I work at yesterday) but I keep getting an error message that I don't 
know what to do about:  
crosis% make
cd ocamlopt-3.05; make
make[1]: *** No rule to make target `asmcomp//arch.ml', needed by 
`asmcomp/arch.ml'.  Stop.
make: *** [ocamlopt-3.05/ocamlopt] Error 2
crosis%

Course I'm not exactly a developer... :^)

-------------------------------------------------------
Date: 2002-Aug-15 10:25             By: agent69
Is this bug being worked on or does mldonkey just need a recompile with 10.2 
Jaguar Developer tools?




No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=975&group_id=1409




reply via email to

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