Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2022-04

crash on startup

6 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Marco van de Voort

I rebuilt Lazarus today (FPC trunk 2 days old -lazarus trunk today), and I suddenly got? a GPF while starting.

I ran under GDB and the traceback is:

Thread 1 received signal SIGILL, Illegal instruction. DOAUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AXPROPORTION=0.80000000000000004,
??? AYPROPORTION=0.80000000000000004) at include/customlistview.inc:684 684?????????? C.MaxWidth := Round(C.MaxWidth * AXProportion); (gdb) bt
#0? DOAUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AXPROPORTION=0.80000000000000004,
??? AYPROPORTION=0.80000000000000004) at include/customlistview.inc:684 #1? 0x00579a1d in AUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/control.inc:4212 #2? 0x0056966e in AUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/wincontrol.inc:3880 #3? 0x00569652 in AUTOADJUSTLAYOUT (this=0x1cb260a0, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/wincontrol.inc:3878 #4? 0x00569652 in AUTOADJUSTLAYOUT (this=0x1cb25b50, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/wincontrol.inc:3878 #5? 0x00435dc5 in AUTOADJUSTLAYOUT (this=0x1cb25b50, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at
include/customdesigncontrol.inc:34
#6? 0x00436a5d in AFTERCONSTRUCTION (this=0x1cb25b50) at include/customform.inc:84
#7? 0x009e788b in CREATE (this=0x1cb25b50, vmt=0x1, THEOWNER=0x1639ac90) at editormacrolistviewer.pas:1614
#8? 0x009e25ee in MACROLISTVIEWER () at editormacrolistviewer.pas:332 #9? 0x009e2a7e in LOADGLOBALINFO () at editormacrolistviewer.pas:418 #10 0x0044f17d in CREATE (this=0x1ac3a020, vmt=0x1, THEOWNER=0x1639ac90) at main.pp:1608
#11 0x00403a51 in main () at lazarus.pp:141
(gdb)

I use anchordocking procedure. Is this a known issue?

Reply by email

Marc Weustink
to Marco van de Voort

The SIGILL here points more to the generated code I think.

Marc

Marco van de Voort wrote 45 lines
I rebuilt Lazarus today (FPC trunk 2 days old -lazarus trunk today), and I suddenly got? a GPF while starting. I ran under GDB and the traceback is: Thread 1 received signal SIGILL, Illegal instruction. DOAUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AXPROPORTION=0.80000000000000004, ??? AYPROPORTION=0.80000000000000004) at include/customlistview.inc:684 684?????????? C.MaxWidth := Round(C.MaxWidth * AXProportion); (gdb) bt #0? DOAUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AXPROPORTION=0.80000000000000004, ??? AYPROPORTION=0.80000000000000004) at include/customlistview.inc:684 #1? 0x00579a1d in AUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/control.inc:4212 #2? 0x0056966e in AUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/wincontrol.inc:3880 #3? 0x00569652 in AUTOADJUSTLAYOUT (this=0x1cb260a0, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/wincontrol.inc:3878 #4? 0x00569652 in AUTOADJUSTLAYOUT (this=0x1cb25b50, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/wincontrol.inc:3878 #5? 0x00435dc5 in AUTOADJUSTLAYOUT (this=0x1cb25b50, AMODE=LAPAUTOADJUSTFORDPI, AFROMPPI=120, ATOPPI=96, ??? AOLDFORMWIDTH=569, ANEWFORMWIDTH=455) at include/customdesigncontrol.inc:34 #6? 0x00436a5d in AFTERCONSTRUCTION (this=0x1cb25b50) at include/customform.inc:84 #7? 0x009e788b in CREATE (this=0x1cb25b50, vmt=0x1, THEOWNER=0x1639ac90) at editormacrolistviewer.pas:1614 #8? 0x009e25ee in MACROLISTVIEWER () at editormacrolistviewer.pas:332 #9? 0x009e2a7e in LOADGLOBALINFO () at editormacrolistviewer.pas:418 #10 0x0044f17d in CREATE (this=0x1ac3a020, vmt=0x1, THEOWNER=0x1639ac90) at main.pp:1608 #11 0x00403a51 in main () at lazarus.pp:141 (gdb) I use anchordocking procedure. Is this a known issue?

Reply by email

Marco van de Voort
to Marc Weustink
Marc Weustink wrote
The SIGILL here points more to the generated code I think.

Indeed, I see what I think are avx512 instructions

?0x005afb7a <+90>:??? call?? 0x5b1040 <GETCOLUMNFROMINDEX> ?? 0x005afb7f <+95>:??? mov??? %eax,-0x10(%ebp)
=> 0x005afb82 <+98>:??? vcvtusi2sd 0x28(%eax),%xmm0,%xmm0 ?? 0x005afb89 <+105>:?? vmulsd 0x10(%ebp),%xmm0,%xmm0 ?? 0x005afb8e <+110>:?? vmovsd %xmm0,-0x20(%ebp)
?? 0x005afb93 <+115>:?? fldl?? -0x20(%ebp)

Reply by email

Marc Weustink
to Marco van de Voort
Marco van de Voort wrote 5 lines
On 1-4-2022 12:57, Marc Weustink via lazarus wrote: > The SIGILL here points more to the generated code I think. Indeed, I see what I think are avx512 instructions

Yes, CPUID Feature Flag AVX512F

Show quoted text 8 lines
?0x005afb7a <+90>:??? call?? 0x5b1040 <GETCOLUMNFROMINDEX> ?? 0x005afb7f <+95>:??? mov??? %eax,-0x10(%ebp) => 0x005afb82 <+98>:??? vcvtusi2sd 0x28(%eax),%xmm0,%xmm0 ?? 0x005afb89 <+105>:?? vmulsd 0x10(%ebp),%xmm0,%xmm0 ?? 0x005afb8e <+110>:?? vmovsd %xmm0,-0x20(%ebp) ?? 0x005afb93 <+115>:?? fldl?? -0x20(%ebp)

Reply by email

Marc Weustink
to Marc Weustink
Marc Weustink wrote 10 lines
On 1-4-2022 14:52, Marco van de Voort via lazarus wrote: > > On 1-4-2022 12:57, Marc Weustink via lazarus wrote: >> The SIGILL here points more to the generated code I think. > > Indeed, I see what I think are avx512 instructions Yes, CPUID Feature Flag AVX512F

SSE2 has only the signed version CVTSI2SD

Show quoted text 9 lines
> ??0x005afb7a <+90>:??? call?? 0x5b1040 <GETCOLUMNFROMINDEX> > ??? 0x005afb7f <+95>:??? mov??? %eax,-0x10(%ebp) > => 0x005afb82 <+98>:??? vcvtusi2sd 0x28(%eax),%xmm0,%xmm0 > ??? 0x005afb89 <+105>:?? vmulsd 0x10(%ebp),%xmm0,%xmm0 > ??? 0x005afb8e <+110>:?? vmovsd %xmm0,-0x20(%ebp) > ??? 0x005afb93 <+115>:?? fldl?? -0x20(%ebp) > >

Reply by email

Marco van de Voort
to Marc Weustink
Marc Weustink wrote 7 lines
>> Indeed, I see what I think are avx512 instructions > > Yes, CPUID Feature Flag AVX512F SSE2 has only the signed version CVTSI2SD

This machine is a Ivy Bridge so has Coreavx ( AVX1) enabled, so some VEX usage is allowed.

I removed some avx1 (-Cpcoreavx -Opcoreavx -Cfcoreavx) from fpc.cfg and the problem went away for more.

I asked on (FPC) core for a quick comment, and will file it as a bug if nobody has a direct hunch. (which would be understandable since I can't pinpoint the exact date when this was introduced)

Reply by email