Paul wrote: > Hi Eric > > On Friday 27 April 2007 17:32, Eric Noulard wrote: >> 2007/4/27, Jan Kiszka <[EMAIL PROTECTED]>: >>>> I mean I know that uninitialized memory have unpredictable consequence >>>> but here the bug is persistent after rerun, reboot, power cycle etc... >>> What is a.sa_flags initialised when it is not initialised? 0? Maybe you >>> can nail it down to defined state that causes the core dump reliably. >>> Then we can also track down what happens to your sigaction call and >>> if/why Xenomai/I-pipe changes the picture in some regard. >> I did rerun as you suggest, find the code attached which >> consistentely core dump with xenomai kernel and (seems to) do nothing >> special with the other kernel. >> >> a.sa_flags = 0xbff81578; > > Try: > > a.sa_flags = 0x04000000; >
Yep, red herring regarding Xenomai. I get the same sigsegv over plain linux here, and looking at that bit above (SA_RESTORER), it also makes sense: this declares sigaction::sa_restorer valid, an internal field that you don't touch/initialise as well. Jan _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
