From: FFADO <ffa...@ff...> - 2010-01-03 09:53:58
|
#247: 896HD only successfully connects in jackd at 192000 -------------------------------------+-------------------------------------- Reporter: sireasoning | Owner: jwoithe Type: bug | Status: assigned Priority: major | Milestone: FFADO 2.1 Version: FFADO 2.0-rc2 (1.999.42) | Resolution: Keywords: | Device_name: Motu 896HD -------------------------------------+-------------------------------------- Comment (by jwoithe): Some more ideas. Assuming that the recompilation of jackd does not change the symptoms, the next thing to try is to get a core dump from jackd and try to work out the general area of the problem. You can skip the next paragraph if you're familiar with obtaining core dumps and using them in gdb. To enable core dumps use "ulimit -c 204800" under bash or "limit coredumpsize 204800" under tcsh. Then run jackd in the usual way, requesting the sample rate which gives rise to the segmentation fault (as opposed to the double-free trap). When jackd crashes now it should create a core file (named core*, the "*" portion depending on your configuration - I'll assume it's empty for the rest of this description). We can then use that core file with gdb to at least find out the function that caused the crash. Start gdb with "gdb /usr/bin/jackd core". Typing the "where" command at the gdb prompt should give a listing of the call stack leading to the crash. One can then use "print" to display variable values in the faulting function, and so forth. Unless memory has been badly corrupted this might give a clue as to what went wrong. I realise the above is rather brief - if you need further information about any of this please let me know and I'll expand as needed. -- Ticket URL: <http://subversion.ffado.org/ticket/247#comment:19> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |