On Wed, 28 Sept 2022 at 16:26, imm wrote:
>
> > For WIN32, I'm puzzled cause it runs here. A debug, or a traceback at the crash point would help.
> >
> What tool are you building with?
> I have mingw, 32-bit - but I'd guess for Win11 on ARM you are using
> the MSVC tools?
>
> I'll try and see if I can get any more insight... might mean doing a
> debug build though!

Well that was profoundly unhelpful: Here is the gdb log from the crash

Reading symbols from
d:\Tools\Ian\fltk-1.4\build\bin\examples\OpenGL3test.exe...done.
(gdb) r
Starting program: d:\Tools\Ian\fltk-1.4\build/bin/examples/OpenGL3test.exe
[New Thread 8612.0x2ac0]
[New Thread 8612.0xaec]
[New Thread 8612.0x2bfc]
[New Thread 8612.0x2790]
[New Thread 8612.0x2008]
[New Thread 8612.0x29d0]
[New Thread 8612.0x2918]
[New Thread 8612.0x287c]

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x01800000 in ?? ()
#2  0x00000000 in ?? ()
(gdb)

Wherever it is segfaulting, it doesn't seem to have enough context to
be able to say where it went awry, even...It appears the frame is zero
at that point.

Also, Albrecht - thanks for the git reflog tip, I'll try that next
time, see if it makes sense to me. At present it shows a lot of churn,
but that's from me trying to bisect the crash of course.

Anybody - does this OpenGL3test.exe work on WinXX x86-64 for you or
not? Is it only me that sees it crashing?

-- 
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/CAGFM6dZpb%2BUFNShhzjpw2gr2EV2nEJ09u_M9QAw0hAQebTWfqg%40mail.gmail.com.