Re: SIG32/SIGSEGV in balsa 2.1.2



On 04/27/2004 10:00:45 AM, tn fenster wrote:
> Hello,
> 
> as I had no success trying to get balsa 2.0.17 working I tried  
> to install balsa 2.1.2 and get the following crash every time I  
> start balsa:
> 
> (gdb) run --disable-crash-dialog
> Starting program: /home/tf/download/internet/balsa/2.1/balsa- 
> 2.1.2/src/balsa --disable-crash-dialog
> audio_alsa: no cards found!
> opening Eingang..
> 
> Program received signal SIG32, Real-time event 32.

I used to have problems with threaded builds on my previous box,  
which had broken sound support, and I sometimes saw that SIG32  
stuff.  Can you disable that alsa check somehow?
[ trace snipped ]

> As this looked like a threading problem to me, I did a  
> configure --disable-threads but this time get a segfault every  
> time I start. Output of gdb is:
> 
> (gdb) run --disable-crash-dialog
> Starting program: /home/tf/download/internet/balsa/2.1/balsa- 
> 2.1.2/src/balsa --disable-crash-dialog
> audio_alsa: no cards found!
> opening Eingang..
> 
> Program received signal SIGSEGV, Segmentation fault.
> libbalsa_condition_clone (cnd=0x0) at filter-funcs.c:416
[ snip ]

That one was fixed in cvs yesterday!  Loading filters from the  
config file was the issue.

> After that I deleted all my filters from the balsa
> configuration file and balsa started ok.

That would also fix it...

> When I tried to check for new mails, the inbox unread count was  
> correctly increased to 1 but I couldn't see the messages. After  
> closing and reopening the message was there,

I don't know what's going on there--I'm using a non-threaded  
build right now, and still see new messages.

> but I got an error message saying: Couldn't sync mailbox  
> Eingang

Ouch!!  Me too...I believe it's time to dump mailbox locking in  
non-threaded builds, it does nothing but prevent recursive  
locking.

Peter




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