Hi, On 2012-12-06 01:03, silverdr@wfmh.org.pl wrote: > > On 2012-12-06, at 00:02, silverdr@wfmh.org.pl wrote: >> >> but then, when I try to use it, x64 hangs and in the logs it says: >> >> Sound: Warning - Buffer drained >> Warning - Your machine is too slow for current settings! >> Received signal 11 (SIGSEGV), exiting. >> >> Exiting... > > And when I run it with -core, I get the crashlog saying > > Process: x64 [92411] > Path: /usr/local/bin/x64 > [...] > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x0000000001d22c88 > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Thread 0 Crashed: Dispatch queue: com.apple.main-thread > 0 libusb-legacy-0.1.4.dylib 0x0000000101c4651f usb_control_msg + 47 > 1 libopencbm-xum1541.dylib 0x0000000101c3d80a xum1541_control_msg + 90 > 2 x64 0x00000001001352f6 realdevice_reset + 29 > 3 x64 0x000000010013331a serial_iec_bus_reset + 14 > 4 x64 0x0000000100134f45 serial_traps_reset + 9 > 5 x64 0x0000000100040f13 machine_specific_reset + 9 > 6 x64 0x0000000100015d24 machine_reset + 56 > 7 x64 0x0000000100027119 cpu_reset + 72 > 8 x64 0x0000000100027a43 maincpu_mainloop + 2280 > 9 x64 0x00000001000163be main_program + 1141 > 10 x64 0x0000000100181ede main + 27 > 11 x64 0x0000000100001c74 start + 52 > [...] > I just did a quick test of ZoomFloppy, OpenCBM and VICE on FreeBSD 9.1 (that was what I had available) and it shows a similar problem: VICE coredump and a somewhat similar call stack trace caused by/in libusb It definitely needs more debugging. /Uffe Message was sent through the cbm-hackers mailing listReceived on 2012-12-06 11:00:41
Archive generated by hypermail 2.2.0.