pico segfaults again because of statusmessage from line 442

[Andrei Kholodnyi]

On Fri, Nov 26, 2010 at 5:32 PM, Halim Sahin <halim.sahin at t-online.de> wrote:
> Hi Andrei,
>
> After writing my last mail to you i did more testing with gdb and pico.c
> Remember we set *status_info=NULL after the gthread lines.
> I found out that the problem of the no accessible pointer starts after
> pico_initialize
> if ((ret = pico_init.....
> and run the function in single steps.
> The problem seems to be a crash in the pico library itself.
> However the check ret = picor_initialize did not catch it.
>
> After that I upgraded to latest git version of the pico which is
> included in debian and now it works.
>
> Can you please have a look to pico.c line 413.
> The condition did not catch the problem in pico library.

sure.
could you please provide more details about that:
"seems to be a crash in the pico library itself" means?

what value does pico_initialize return?
if it crashes inside and still returns 0 it will be difficult to catch :D

Thank much for your debugging
Andrei.