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: [commit] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones


On Mon, 07 May 2018 10:02:57 +0200, Omair Javaid wrote:
> On 5 May 2018 at 01:47, Pedro Alves <palves@redhat.com> wrote:
> > On 05/04/2018 09:30 PM, Jan Kratochvil wrote:
> >> Checked in:
> >>       a3b60e4588606354b93508a0008a5ca04b68fad8
> 
> New watchpoint-unaligned.exp test introduced by this commit fails for
> arm targets. (Tested with Raspberry Pi2 Tester)

I have described that in the commit log:
    There remains one issue:
            kernel-4.15.14-300.fc27.armv7hl
            FAIL: gdb.base/watchpoint-unaligned.exp: continue
            FAIL: gdb.base/watchpoint-unaligned.exp: continue
            (gdb) continue
            Continuing.
            Unexpected error setting watchpoint: Invalid argument.
            (gdb) FAIL: gdb.base/watchpoint-unaligned.exp: continue
    But that looks as a kernel bug to me.
    (1) It is not a regression by this patch.
    (2) It is unrelated to this patch.

I do not have ARM32 machine for testing, I did find out the FAIL on
	https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
	arm03-packager00.cloud.fedoraproject.org
	arm03-packager01.cloud.fedoraproject.org
but that does not have too recent kernel and I haven't found an ARM32 machine
with newer kernel, both such allocations failed for me inside Red Hat:
	Fedora-28-20180427.n.0      armhfp https://beaker.engineering.redhat.com/recipes/5107255
	Fedora-Rawhide-20180502.n.0 armhfp https://beaker.engineering.redhat.com/recipes/5106357
due to:
	Question      
	The following error occurred while installing the boot loader. The system will 
	not be bootable. Would you like to ignore this and continue with installation? 
	boot loader install failed      
	Please respond 'yes' or 'no':

It is true I could file some tracker PR for such XFAIL but then it looks to me
as it would get more easily forgotten while this existing ARM32 bug unrelated
to this my aarch64 fix should be probably fixed soon.

One should also bisect GDB if it isn't a regression. But TBH professionally
AFAIK I am also not so much interested in ARM32.


> I have not tested it for other targets but if this is AArch64 specific
> kindly mark it an XFail for other targets.

I have marked it as XFAIL for all targets where it makes sense and which
I could test.


Jan


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