DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=JWeVZNiRO8TBuDQ9TJQ7JgQbdla59hyHDTLa0t5yiDO
	isU9eWsypjQVq8JQVCfHU3xG2igW+dkmcLLCFFPLgtUmHStNNEDKXjzKApd/l7pw
	2yfsmZqY6rcH82lpnYkAcSF2Ui5WtCmSoZXTPvPp9KJ/6kHN4QfI0K+ZMISDs8/4
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <54EC98B4.9050003@dronecode.org.uk>
Date: Tue, 24 Feb 2015 15:28:52 +0000
From: Jon TURNEY <jon.turney@dronecode.org.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [PATCH] Teach gdb how to unwind cygwin _sigbe frames
References: <1424715301-13516-1-git-send-email-jon.turney@dronecode.org.uk> <20150223212427.GB437@calimero.vinschen.de>
In-Reply-To: <20150223212427.GB437@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 23/02/2015 21:24, Corinna Vinschen wrote:
> On Feb 23 18:15, Jon TURNEY wrote:
>> I really wanted to do this by adding some DWARF CFI to the generated sigfe.s
>> file, but there doesn't seem to currently be a way to correctly describe
>> _sigbe's frame using that.
>
> I was wondering about this already.  It seems weird if the CFI stuff
> doesn't allow for a situation like that

My understanding is limited, but it seems to me that it only describes 
register unwinding, not unwinding the state of an arbitrary memory location.

After writing my patch, which only unwinds one sigstack entry correctly, 
I went back and had another go at writing the equivalent CFI, which I 
think should be possible, but I still couldn't get it to work.

I'll take another look.

>> So instead, write a custom unwinder for _sigbe frames, which gets the return
>> address from the sigstack.
>>
>> Implemented for i386 and amd64.
>
> Cool.  Really.  But, shouldn't that go to the gdb-patches mailing list?
>
>> 4. This unfortunately ends up hardcoding into gdb the offset of sigstackptr in
>> the cygwin TLS area from the top of stack, and so will break if that changes.
>> Hopefully that doesn't happen to often.
>
> It happens too often to be ignored.  Wouldn't it make sense to add
> a cygwin_internal call to return tls offsets or addresses, the later
> if the argument is a pointer to the stack or cygtls area?

That's not going to give the right answer when remote debugging.

But the offset is, of course, encoded into the _sigbe routine, so the 
better approach is probably to extract it from there.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple