Lazarus 0.9.24 External SIGSEV without obvious reason lazarus / 12-Debugger ---------------------------------------------------------------------- cyber_python · 2007-11-28 23:22 Yesterday I installed Lazarus 0.9.24 (clean install - I uninstalled Lazarus 0.9.22 first) on my WinXP Home system. When I tried to run a project with just a form, it compiled but the debugger  gave the error : project raised exception class'External SIGSEV' and then I got the message: Execution paused Address: $10008761 Procedure U_WIN32UXTHEME_LOCK File: (Some day..........) I tried many times with other projects, empty forms, I uninstalled and re-installed but it keeps firing this error.... Does anyone know what's wrong? ---------------------------------------------------------------------- Leledumbo · 2007-11-29 07:59 Quote Execution paused Address: $10008761 Procedure U_WIN32UXTHEME_LOCK File: Just guessing, do you use any uxtheme patcher? (Once again, it's JUST a guess!) ---------------------------------------------------------------------- Marc · 2007-11-29 10:34 Can you post the lines of the view-debugger-debugger output window ? ---------------------------------------------------------------------- cyber_python · 2007-11-29 11:25 Yes, I am using StyleXP, but everything worked fine up to Lazarus 0.9.22 . The debugger output is the following : "C:/DOCUME~1/CYBER_~1/LOCALS~1/Temp/project1.exe"> ^done (gdb) <-environment-cd "C:/DOCUME~1/CYBER_~1/LOCALS~1/Temp/"> ^done (gdb) <-data-evaluate-expression FPC_THREADVAR_RELOCATE_PROC> ^done,value="0x0" (gdb) <-exec-arguments > ^done (gdb) <-gdb-set language pascal> ^done (gdb) &"info address main\n" ~"Symbol \"main\" is a function at address 0x402580.\n" ^done (gdb) <-break-insert -t *4203904> ^done,bkpt={number="1",type="breakpoint",disp="del",enabled="y",addr=" 0x00402580",func="main",file="project1.lpr",fullname="C:/DOCUME~1/CYBE R_~1/LOCALS~1/Temp/project1.lpr",line="13",times="0"} (gdb) <-break-insert FPC_RAISEEXCEPTION> ^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr= "0x00408d36",func="fpc_raiseexception",file="except.inc",line="189",ti mes="0"} (gdb) <-break-insert FPC_BREAK_ERROR> ^done,bkpt={number="3",type="breakpoint",disp="keep",enabled="y",addr= "0x0040a1e0",func="HANDLEERRORADDRFRAME",file="system.inc",line="794", times="0"} (gdb) <-break-insert FPC_RUNERROR> ^done,bkpt={number="4",type="breakpoint",disp="keep",enabled="y",addr= "0x0040a2d3",func="RUNERROR",file="system.inc",line="837",times="0"} (gdb) &"info file\n" ~"Symbols from \"C:/DOCUME~1/CYBER_~1/LOCALS~1/Temp/project1.exe\".\n" ~"Local exec file:\n" ~"\t`C:/DOCUME~1/CYBER_~1/LOCALS~1/Temp/project1.exe', file type pei-i386.\n" ~"\tEntry point: 0x4d47a0\n" ~"\t0x00401000 - 0x004d47c0 is .text\n" ~"\t0x004d5000 - 0x00514fc8 is .data\n" ~"\t0x00515000 - 0x00529860 is .bss\n" ~"\t0x0052a000 - 0x0052c4c0 is .idata\n" ^done (gdb) <-exec-run> ^running (gdb) *stopped,reason="signal-received",signal-name="SIGSEGV",signal- meaning="Segmentation fault",thread- id="1",frame={addr="0x10008751",func="U_WIN32UXTHEME_LOCK",args=[]} (gdb) <-stack-info-depth> ^done,depth="2" (gdb) <-stack-list-arguments 1 0 0> ^done,stack-args=[frame={level="0",args=[]}] (gdb) <-stack-list-frames 0 0> ^done,stack=[frame={level="0",addr="0x10008751",func="U_WIN32UXTHEME_L OCK"}] (gdb) <-stack-list-arguments 1 1 1> ^done,stack-args=[frame={level="1",args=[]}] (gdb) <-stack-list-frames 1 1> ^done,stack=[frame={level="1",addr="0x00000000",func="?"}] (gdb) &"info program\n" ~"\tUsing the running image of child thread 1308.0x11ac.\n" ~"Program stopped at 0x10008751.\n" ~"It stopped with signal SIGSEGV, Segmentation fault.\n" ~"Type \"info stack\" or \"info registers\" for more information.\n" ^done (gdb) <-exec-continue> ^running (gdb) *stopped,thread-id="1",frame={addr="0x00402580",func="main",args=[],fi le="project1.lpr",fullname="C:/DOCUME~1/CYBER_~1/LOCALS~1/Temp/project 1.lpr",line="13"} (gdb) ---------------------------------------------------------------------- Marc · 2007-11-29 13:56 lazarus 0.9.22 had no theming support. 0.9.24 has. So somehow the thememanager breaks your theme. Can you try your app without generating a manifest ? (see project options) ---------------------------------------------------------------------- Marc · 2007-11-29 14:09 ???? WIN32UXTHEME is one of our units and LOCK is a local variable So why an SIGSEGV on the lock procedure I'm puzzeled. Can you try running your app with a breakpoint in the initialization section of win32uxtheme.pas and see if it reaches that point ? ---------------------------------------------------------------------- cyber_python · 2007-12-02 09:07 I can't figure out what is wrong!!! I tried setting a breakpoint before and after the initialization section of WIN32UXTHEME but the debugger first shows the error and then I get the red line indication that I have reached the selected line. When placing the breakpoint right on the "initialization" line I got the error, then the red line indication that I have reached the selected line and then it turned grey. An interesting fact is that programs compile, and run normally outside the IDE, so I selected none in the debugger options and it works. Any ideas? ---------------------------------------------------------------------- reneve59 · 2007-12-02 15:58 I've experimented the same problem. I upgraded from lazarus 0.9.22 to 0.9.24, I' using WinXP on a Presario V2000 Notebook with an AMD Turion64 processor, 1 Gb of ram and an ATI Radeon Xpress 200M graphics card. I did the same procedure on a Toshiba Satellite, with an Intel Centrino processor and WinXP and the problem does not appear on this one I both cases Win32 version of Lazarus was used (0.9.22 upgraded to 0.9.24) and the problem did not appear with 0.9.22 release. ---------------------------------------------------------------------- cyber_python · 2007-12-02 17:55 My system is an Intel Core 2, 2Gb RAM, Nvidia Geforce 8400GS 512Mb. So I guess it has not to do with the processor or the gpu or hardware setup generally. ---------------------------------------------------------------------- Vincent Snijders · 2007-12-02 21:52 There are a lot of changes between 0.9.22 and 0.9.24. One of them is the version of the debugger: from gdb 6.0 to gdb 6.6. ---------------------------------------------------------------------- reneve59 · 2007-12-03 01:48 Quote from: "cyber_python"My system is an Intel Core 2, 2Gb RAM, Nvidia Geforce 8400GS 512Mb. So I guess it has not to do with the processor or the gpu or hardware setup generally. Hi, after reading your response, I  tested Lazarus with a different version of gdb.exe. As Lazarus 0.9.24 uses FPC 2.2.0, I renamed the gdb.exe  located in mingw\bin directory to gdb-orig.exe (just in case things go wrong), and replaced it with the version that comes with FPC 2.2.0, which is gdb.exe (6.3) This has solved the problem when running applications from the ide , but I don't know if there will be problems when debugging. Have to do more tests. ---------------------------------------------------------------------- masonwheeler · 2008-01-11 19:59 I'm seeing SIGSEV errors a lot too.  I'm running Lazarus 0.9.24 on XP Home.  I haven't implemented any manifests.  I see them often when running TOpenDialog.Execute() if I leave the box open too long.  (In other words, if I don't select a file to open within a few seconds.)  No idea why.  I'll post a stack trace next time I see it.