From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 94339 invoked by alias); 8 Feb 2020 20:15:03 -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 94294 invoked by uid 89); 8 Feb 2020 20:15:01 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=hear X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 08 Feb 2020 20:15:00 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:49180) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1j0WVH-0005tE-Co; Sat, 08 Feb 2020 15:14:59 -0500 Received: from [176.228.60.248] (port=2742 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1j0WVF-0003FM-UQ; Sat, 08 Feb 2020 15:14:59 -0500 Date: Sat, 08 Feb 2020 20:15:00 -0000 Message-Id: <83pneodefj.fsf@gnu.org> From: Eli Zaretskii To: Simon Marchi CC: ssbssa@yahoo.de, gdb-patches@sourceware.org In-reply-to: (message from Simon Marchi on Sat, 8 Feb 2020 15:04:23 -0500) Subject: Re: [PATCH v2 2/2] Use enums for human-readable exception information. References: <20200208162614.4918-1-ssbssa@yahoo.de> <20200208162614.4918-2-ssbssa@yahoo.de> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00246.txt.bz2 > From: Simon Marchi > Date: Sat, 8 Feb 2020 15:04:23 -0500 > > Eli, same question here. This makes GDB's EXCEPTION_RECORD type deviate from > the official one, but just to improve readability when you print it. I think > it's a good idea, but I'd like to hear what you think. This LGTM. > And again, should we document this behavior in the manual, or is it obvious and > discoverable enough by itself (when the user prints $_siginfo, it should be > self-explanatory, if they already know about the real EXCEPTION_RECORD type). Only in NEWS, I think. Thanks.