I've noticed an interesting problem I seem to have acquired, and I was wondering if anyone has come across it before. I used to have a nice, happy installation of lazarus .9.28.2 on Windows Vissta, but I seem to have borked it. Now, no matter how simple an application I build is (IE: 1 Form, no LCL, etc.), when I run programs through the IDE with F9 (or the button), they segfault immediately. I have no idea what the last thing I did was, and I have no idea how to remedy the problem.

What would be a recommend course of action?
- I don't know how I caused this, so I'm not sure if this is a bug
- Is it possible to track down what's causing this?
- Should I reinstall Lazarus? Or should I install an SVN version, for kicks? -------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20100327/f385b845/attachment.html>

Have you upgraded or changed your Antivirus software (or maybe it had an internal update)? Have you tried to run your apps while the anti virus is off (or in game mode).

I have that problem with bit defender.

Martin

Run the program in a debugger and create a backtrace.

- Should I reinstall Lazarus? Or should I install an SVN version, for kicks?

Mattias

Martin

I had already tried that, to no avail

Mattias

It was my understanding that I had to run my program through a debugger (like GDB) outside of the IDE, in which case the application will work flawlessly. It only manages to crash with F9 -- is there a way to debug through that only? I have -g, -gl, -gw, and -Xg enabled. I have a hunch if I run the program with F9 with -Xg enabled (external file with debugging info), there would be a way to parse the generated file, but I've yet to find out how.

On Sat, Mar 27, 2010 at 1:22 PM, Mattias Gaertner <

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20100327/28b19105/attachment-0001.html>

I think I'll update this real quick:
1. I'm using GDB 5.2.1
2. GDB quotes itself as encountering an internal error when I do "gdb project1.exe"
3. I hit no (I don't want to quit) to continue anyway.
4. Run
5. Segfault! Hey.. I actually didn't expect that.

The backtrace:
Program received signal SIGSEGV, Segmentation fault. 0x100177b7 in ?? ()
(gdb) backtrace
#0 0x100177b7 in ?? ()
#1 0x10017af6 in ?? ()
#2 0x100029a0 in ?? ()
#3 0x1000dffe in ?? ()
#4 0x76e9c8f9 in ?? ()
#5 0x76e9cbc3 in ?? ()
#6 0x76e9ec16 in ?? ()
#7 0x75ed96a8 in ?? ()
#8 0x75ed9738 in ?? ()
#9 0x75da08d2 in ?? ()
#10 0x75d75151 in ?? ()
#11 0x75d74e10 in ?? ()
#12 0x75d73f87 in ?? ()
#13 0x76eda604 in ?? ()
#14 0x76e9c8f9 in ?? ()
#15 0x76ea4c41 in ?? ()
#16 0x76ea5ad7 in ?? ()
#17 0x76eaa980 in ?? ()

But I've not the slightest idea what to do with it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20100327/f7695942/attachment.html>

And one more backtrace, after I discovered -Xs was being forced upon compiled programs, removing symbols.

Starting program: C:\Users\Matt\Documents\TestCase/project1.exe

Program received signal SIGSEGV, Segmentation fault. 0x100177b7 in U_SYSINITPAS_ENTRYINFORMATION ()
(gdb) backtrace
#0 0x100177b7 in U_SYSINITPAS_ENTRYINFORMATION ()
#1 0x8c87c83d in ?? ()
#2 0x10017af6 in U_SYSINITPAS_ENTRYINFORMATION ()
#3 0x100029a0 in U_SYSINITPAS_ENTRYINFORMATION ()
#4 0x1000dffe in U_SYSINITPAS_ENTRYINFORMATION ()
#5 0x76e9c8f9 in U_SYSINITPAS_ENTRYINFORMATION ()
#6 0x76e9cbc3 in U_SYSINITPAS_ENTRYINFORMATION ()
#7 0x76e9ec16 in U_SYSINITPAS_ENTRYINFORMATION ()
#8 0x75ed96a8 in ?? ()
#9 0x75ed9738 in ?? ()
#10 0x75da08d2 in ?? ()
#11 0x75d75151 in ?? ()
#12 0x75d74e10 in ?? ()
#13 0x75d73f87 in ?? ()
#14 0x76eda604 in U_SYSINITPAS_ENTRYINFORMATION () #15 0x76e9c8f9 in U_SYSINITPAS_ENTRYINFORMATION () #16 0x76ea4c41 in U_SYSINITPAS_ENTRYINFORMATION () #17 0x76ea5ad7 in U_SYSINITPAS_ENTRYINFORMATION () #18 0x76eaa980 in U_SYSINITPAS_ENTRYINFORMATION () (gdb) q

So yeah, it dies really early into execution. I'm just going to reinstall Lazarus, as this seems like the best option for me.

(Although I still am curious as to why an app segfaults when being debugged, but not when run without a debugger attached...)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20100327/f1fa2062/attachment-0001.html>

I think I'll update this real quick: 1. I'm using GDB 5.2.1

Maybe this is too old. I hope a windows user can tell more.

2. GDB quotes itself as encountering an internal error when I do "gdb project1.exe"

That's pretty bad. I would search for a newer gdb.

Mattias

Well, I updated to the absolute latest I could find, 7.1, and it no longer encounters an internal error, but it still reports the segfault like 5.2.1 did, and as the Lazarus IDE does.

Is it possible for installed packages to cause this problem?

On Sat, Mar 27, 2010 at 4:16 PM, Mattias Gaertner <

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20100327/bc28129e/attachment.html>