Re: [jazzplusplus-devel] configure.ac update -please test-

[D.B. M. <db...@ho...>]

----------------------------------------
> Date: Thu, 15 May 2008 02:14:28 +0000
> Subject: Re: [jazzplusplus-devel] configure.ac update -please test-
> 
> 
> Greetings,
> 
> ----------------------------------------
>> Date: Tue, 13 May 2008 21:38:17 -0700
>> Subject: Re: [jazzplusplus-devel] configure.ac update -please test-
>> 
>> DM = D.B. Moore
>> DM> Yep, no problem.... the back trace without vkeybd
>> DM> running but with jack/fluidsynth/qsynth running
>> DM> and ready to go (complete session);
>> 
>>> Program received signal SIGSEGV, Segmentation fault.
>>> [Switching to Thread 140090596853472 (LWP 3341)]
>>> snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) at seq.c:2432
>>> 2432            memcpy(&info->sender, addr, sizeof(*addr));
>>> Current language:  auto; currently c
>>> 
>>> (gdb) bt
>>> #0  snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0)
>>>     at seq.c:2432
>>> #1  0x0000000000426a59 in tAlsaPlayer::subscribe_inp (this=0xb68020, inp=0)
>>>     at ../../jazz/src/AlsaPlayer.cpp:219
>> 
>> My current guess is an invalid input or output device index.  Could you 
>> update you source tree, rebuild, run again and let me know how it goes?
>> 
> 

I had a closer look at this problem just now....here's what I've found ;

~/Jazz++/TestInstall/bin# aconnect -l -o
client 130: 'AlsaModularSynth' [type=user]
    0 'ams             '
        Connected From: 129:0
client 131: 'FLUID Synth (qsynth)' [type=user]
    0 'Synth input port (qsynth:0)'
        Connected From: 129:0

~/Jazz++/TestInstall/bin# aconnect -l -i
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
        Connecting To: 128:0, 129:0
client 130: 'AlsaModularSynth' [type=user]
    1 'ams             '
        Connecting To: 129:0[real:0]
    2 'ams             '
        Connecting To: 129:0[real:0]


Qsynth is not creating/registering any alsa_input_ports,
whereas AMS (and vkeybd) do.

If I start jazz and  if finds no alsa_input_ports, it will
*not* pop the 'select input' dialog window, and instead
continue bravely forth and pop the 'select output' dialog
window instead.

In this condition, it doesn't matter which output port
is selected, clicking on 'OK' to confirm the output selection
results in the crash observed.

Provided jazz finds at least one (or more) valid alsa_input_ports
to try and connect to at init, the 'select input' dialog box is
displayed, followed by the 'select output' dialog box, and jazz
starts and runs as currently expected.

Regards,

Donald B   
_________________________________________________________________
Search for local singles online @ Lavalife - Click here
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT