From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24725 invoked by alias); 21 Jan 2016 18:22:58 -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 24699 invoked by uid 89); 21 Jan 2016 18:22:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Received-From:4830, HX-Received-From:134, HX-Received-From:2001, HX-HELO:eggs.gnu.org X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Thu, 21 Jan 2016 18:22:57 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMJsh-0006kH-H0 for gdb-patches@sourceware.org; Thu, 21 Jan 2016 13:22:54 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49941) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMJsh-0006k7-EU; Thu, 21 Jan 2016 13:22:51 -0500 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4480 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aMJsg-0007op-IU; Thu, 21 Jan 2016 13:22:51 -0500 Date: Thu, 21 Jan 2016 18:22:00 -0000 Message-Id: <83egda94hi.fsf@gnu.org> From: Eli Zaretskii To: Pedro Alves CC: walfred.tedeschi@intel.com, brobecker@adacore.com, gdb-patches@sourceware.org In-reply-to: <56A11E0E.80403@redhat.com> (message from Pedro Alves on Thu, 21 Jan 2016 18:06:06 +0000) Subject: Re: FW: [PATCH V4 6/6] Intel MPX bound violation handling. Reply-to: Eli Zaretskii References: <1453387705-6597-1-git-send-email-walfred.tedeschi@intel.com> <1453387705-6597-7-git-send-email-walfred.tedeschi@intel.com> <83vb6m9a0u.fsf@gnu.org> <56A11694.4000502@intel.com> <83io2m95yt.fsf@gnu.org> <56A11E0E.80403@redhat.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2016-01/txt/msg00546.txt.bz2 > Date: Thu, 21 Jan 2016 18:06:06 +0000 > From: Pedro Alves > CC: palves@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org > > Program received signal SIGSEGV, Segmentation fault > Upper bound violation while accessing address 0x60302f > Bounds: {lbound = 0x603010, ubound = 0x603023} > > Note we still repeat the string "bound" 4 times. Maybe we > could reduce that: > > Program received signal SIGSEGV, Segmentation fault > Upper bound violation while accessing address 0x60302f > Bounds: [lower = 0x603010, upper = 0x603023] > > But maybe lbound/ubound already have defined meaning to > the user. Both variants are fine, IMO. Thanks.