Kolja Waschk wrote:
>>> file cond-torture-posix
>> Ok. On my side: I call set solib-absolute-prefix to where the debug
>> binaries for the target filesystem are. And I call
>> handle SIG34 nostop noprint pass.
>>
>> Coud you try and do the same?
>
> Is SIG34 the same on blackfin? I do not remember ever having seen SIG34, only
> SIG32 ("Real-time event 32")
>
> Independent of that, the result is always the same SEGV. I cannot use the
> absolute-prefix currently, as the directory layout is different on the
> target. So my script is now
>
> set solib-absolute-prefix notexistent
> set solib-search-path
> /opt/uClinux/blackfin-linux-dist/staging/usr/lib:/opt/uClinux/bfin-linux-uclibc/bfin-linux-uclibc/runtime/lib
> file cond-torture-posix
> handle SIG34 nostop noprint pass
> target remote 10.0.10.9:2222
>
> And regardless whether I add an "break main", the SEGV will occur immediately
> after telling gdb to "cont".
>
> Does my "try.c" always succeed (all errbits=0x0010) in your environment?
Ok, I get the failure if I set up a breakpoint right after the call to
pthread_cond_wait, as noted by Pierre. After some debugging, it appears
that the syscall is restarted whereas it should return to user-spacce
and let the user-space skin do its job. So, it seems that somehow, the
behaviour is different for gdb signals than for usual signals.
Working on it now, will tell you when we have a status.
--
Gilles.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
