This is the mail archive of the
mailing list for the Cygwin project.
Re: [64bit] Problem with emacs and shared memory under X11
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 19 Jul 2013 18:18:17 +0100
- Subject: Re: [64bit] Problem with emacs and shared memory under X11
- References: <51D803A0 dot 7090700 at cornell dot edu> <51D82992 dot 5010402 at dronecode dot org dot uk> <51E70D37 dot 5020600 at dronecode dot org dot uk> <20130718083748 dot GA9628 at calimero dot vinschen dot de> <51E858E2 dot 7050802 at dronecode dot org dot uk> <20130718213455 dot GC30542 at calimero dot vinschen dot de> <51E91378 dot 6060402 at dronecode dot org dot uk> <20130719113509 dot GF20871 at calimero dot vinschen dot de> <51E96374 dot 4080308 at cornell dot edu> <20130719171104 dot GI20871 at calimero dot vinschen dot de>
On 19/07/2013 18:11, Corinna Vinschen wrote:
> On Jul 19 12:04, Ken Brown wrote:
>> On 7/19/2013 7:35 AM, Corinna Vinschen wrote:
>>> On Jul 19 11:22, Jon TURNEY wrote:
>>>> Oh yes, that works, and is a bit clearer.
>>> Thanks for testing. I applied the patch and attributed it to you in
>>> the ChangeLog since you did all the work anyway.
>> There's still the x86 issue that I mentioned earlier. With
>> cygwin-1.7.21 (as well as today's snapshot), I'm getting a return
>> value of 0 from shmtest on x86. This is with cygserver not running.
>> (In fact, cygserver has never been configured on this system, so
>> there's no /etc/cygserver.conf). Jon reported getting a return
>> value of 1 using cygwin-1.7.20.
> I don't recall seeing this testcase. Any chance you can extract an STC
> to help fixing this? I wonder how this happened anyway. There were no
> changes in terms of XSI IPC between 1.7.20 and 1.7.21, except for tiny
> changes for porting to x86_64. What on earth did I screw up this
shmtest.c was attached to my mail a couple of days ago 
This seems to be an unrelated issue. When cygserver is not running, this
program should receive a SIGSYS and terminate with exit code 140 (128 + signal)
This works correctly on x86_64, but on x86, although the signal is raised,
something goes wrong and the exit code is 0...