RE: x86_64-m32 internal error for multi-thread-step.exp [Re: [PATCH v10 06/28] btrace: change branch trace data structure]

Metzger, Markus T
2015-01-20T15:19:25Z

> -----Original Message-----
> From: Jan Kratochvil [mailto:jan.kratochvil@redhat.com]
> Sent: Thursday, January 8, 2015 9:50 PM
> To: Metzger, Markus T
> Cc: palves@redhat.com; gdb-patches@sourceware.org
> Subject: x86_64-m32 internal error for multi-thread-step.exp [Re: [PATCH
> v10 06/28] btrace: change branch trace data structure]

Thanks, Jan,

> Although for -m32 inferior there are 100% reproducible more FAILs:
> FAIL: gdb.btrace/rn-dl-bind.exp: reverse-next
> FAIL: gdb.btrace/rn-dl-bind.exp: reverse-step
> FAIL: gdb.btrace/rn-dl-bind.exp: reverse-step
> FAIL: gdb.btrace/rn-dl-bind.exp: reverse-next
> FAIL: gdb.btrace/rn-dl-bind.exp: next (the program exited)
> FAIL: gdb.btrace/exception.exp: flat (pattern 1)
> FAIL: gdb.btrace/exception.exp: indented (pattern 1)

I can reproduce those fails and will look into them.

> btrace.c:220: internal-error: ftrace_new_function: Assertion `prev-
> >flow.next == NULL' failed.^M
>
> This occasionally happens on x86_64 system with -m32 inferior:
> runtest CC_FOR_TARGET="gcc -m32" CXX_FOR_TARGET="g++ -m32"
> gdb.btrace/multi-thread-step.exp

I can't reproduce this fail; I don't get that far. This test fails for me with

FAIL: gdb.btrace/multi-thread-step.exp: continue to breakpoint: cont to multi-thread-step.c:34 (timeout)

This fail can be reproduced also with 64-bit inferiors and it looks like a regression
to end of last year. The test passed when I sent the patch series. I'll look into
this first.

Regards,
Markus.

Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052