From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41428 invoked by alias); 7 Feb 2020 22:07:09 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 41419 invoked by uid 89); 7 Feb 2020 22:07:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=H*M:cdfc X-HELO: simark.ca Received: from simark.ca (HELO simark.ca) (158.69.221.121) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 07 Feb 2020 22:07:08 +0000 Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 306C31E05A; Fri, 7 Feb 2020 17:07:06 -0500 (EST) Subject: Re: [PATCH 1/2] Display ExceptionRecord for $_siginfo From: Simon Marchi To: Hannes Domani , gdb-patches@sourceware.org References: <20200117153140.2231-1-ssbssa.ref@yahoo.de> <20200117153140.2231-1-ssbssa@yahoo.de> <544d0a3a-bee9-1ac6-8f4b-611ccbcc39bb@simark.ca> Message-ID: <79d771b0-ec85-cdfc-e966-a61c6bb9b59f@simark.ca> Date: Fri, 07 Feb 2020 22:07:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <544d0a3a-bee9-1ac6-8f4b-611ccbcc39bb@simark.ca> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-02/txt/msg00194.txt.bz2 Btw, as mentioned here: https://docs.microsoft.com/en-us/windows/win32/api/winnt/ns-winnt-exception_record#remarks The layout of the structure is different depending on if the debugged process is 32 or 64 bits. >From what I understand, you code adapts to both, since it uses gdbarch_ptr_bit and uses proper alignment for the ExceptionInformation field, but I wanted to point it out just to be sure. Simon