From: Paul F. <pf...@ta...> - 2003-09-18 09:08:28
|
Jeff, Yes the behaviour is different from the host. However looking at the signal handling (with the DDD front end). I've notice that on the host the SIG32 signal (Real-time event 32) is neither "stopped" nor "printed". Changing the signal handling on the UML node to match the host fixes my problem, allowing my program to create threads. I am noticing that running DDD on the host and GDB on the UML node is a bit slow and unreliable (lose DDD->GDB connection), but I'm not sure which component to blame (DDD, GDB, UML)? > ddd --host <user>@<host> <program> Now I'll have to find where the default signal handling behaviour is stored - most likely DDD or GDB preferences. Perhaps the GDB preferences are different in the Slackware 8.1 filesystem that I'm using for UML. Thanks for you help, Paul Jeff Dike wrote: > pf...@ta... said: > >>1) My program calls pthread_create() >>2) Signal SIG32 is received and debugging stops: >>Program received signal SIG32, Real-time event 32. >>0x40068469 in sigsuspend () from /lib/libc.so.6 >>3) Program stack trace is: >>my_function() -> pthread_create() -> pthread_getconcurrency() -> >>sigsuspend() > > > Is this different behavior from the host? pthreads does use SIGRT* to > communicate between threads, I believe, and gdb is well within its rights > to report that to you. > > Jeff > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > User-mode-linux-user mailing list > Use...@li... > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user > |