From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter Soetens <peter@domain.hid>
Date: Tue, 16 Mar 2010 13:29:32 +0100
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201003161329.32546.peter@domain.hid>
Subject: [Xenomai-help] xeno_sigwinch_handler causes segfault with readline
List-Id: Help regarding installation and common use of Xenomai
	<xenomai.xenomai.org>
List-Unsubscribe: <https://mail.gna.org/listinfo/xenomai-help>,
	<mailto:xenomai-help-request@domain.hid>
List-Archive: </public/xenomai-help>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-help-request@domain.hid>
List-Subscribe: <https://mail.gna.org/listinfo/xenomai-help>,
	<mailto:xenomai-help-request@domain.hid>
To: xenomai-help <xenomai@xenomai.org>

I'm testing with (don't shoot me)
* 2.6.31.1-ipipe-2.4-07 #3 SMP
* Xenomai 2.4.93 (please!)

But a user reported with:
* Kernel 2.6.32.7
* Xenomai 2.5.1 

the same issue. When we first shadow the main thread and then call into 
readline code, we get segfaults, pointing to xeno_sigwinch_handler.

According to docs, we need to be careful when installing a signal handler on 
winch after shadowing. Is this still the issue (I suppose so), or why don't we 
get a nice( that's relative) 'abort' explaining what to do instead of a 
segfault ? 

I'll delve into libreadline to see on how to override/disable the winching by 
readline, but I hope there is some standard solution, maybe by one of the 
Xenomai users.

Cheers,
Peter