This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: FW: [PATCH V4 6/6] Intel MPX bound violation handling.


> Date: Thu, 21 Jan 2016 18:06:06 +0000
> From: Pedro Alves <palves@redhat.com>
> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]