Just yesterday I installed Fedora and find it very surprising that for the first time in my life Lazarus doesn't work. It just throws out without even showing any Window, with exception "out of memory" to console

After that I tried with fpc 1.9, same result except MessageBox "Out of Memory" showed up.

I even recompiled fpc 1.0.10 if some libraries would be mismatched in binary, but there was the same result as before.

Now I'm stuck with a real problem. If there's no solution I would have to abandon one of those two. But problem is that Fedora is just to great to go back, as snappy Linux as Fedora is, well it reminds people on times when user interfaces were simple, light fast and responsive as possible. Difference in speed to RH9 I was using before is impossible to compare.

Well, fact is that not having Fedora on my notebook is not really hard to imagine, all it would need it would be to stop coding during my breaks and when I'm as it seems Fedora as good as it is will probably sooner gain than loose people. At least those who missed apt and other goodies.

I'm not an expert but that maybe a clue. There are 3 major differences between RH9 and Fedora.
1. nptl threads
2. Prelinking: From an end user perspective, it will make applications load faster, as dynamicly linked libraries will be loaded ahead of time into unused memory.
3. Exec-Shield: Exec-shield purports to randomize VM addresses and make parts of applications (as well as their stack) non-executable. Think of it as "damage control" for security holes. The integrated stack protection (that the Exec-shield kernel addition replaces/includes) is very important for foiling buffer overflow attacks

Funny thing is, all other software RH9 rpms that I tried are working as they should, out of src.rpm or rpm.

btw. lazarus was tried only by compiling from 4 different cvs versions (1 from yesterday and 3 versions which were working perfectly on RH9) which I found on my disk.

I don't know if that helped anything but here it is anyway

^^

I hope that I did correct thing^^. And as you see funny thing is that everytime lazarus is runned different problem occurs at least visually, report is almost the same

Correct temporary solution for me was as Tom Lisjac suggested>> install from rpm on lazarus-ccr

Tx for help^^

with fpc-1.9
(gdb) run
Starting program: /home/matooo/Applications/lazarus/lazarus [Thread debugging using libthread_db enabled]
[New Thread -1084347488 (LWP 3616)]
[FORMS.PP] ExceptionOccurred
Sender=EOutOfMemory
Exception=Out of memory
TApplication.HandleException Out of memory

Program exited normally.

with fpc-1.0.11

WARNING: [TgtkObject.StretchBlt] Destination and/or Source unsupported!! [FORMS.PP] ExceptionOccurred
Sender=EACCESSVIOLATION
Exception=Access violation
TApplication.HandleException Access violation
TApplication.HideAllFormsWithStayOnTop :TSPLASHFORM

with fpc-1.0.11 (runned for the second time)

[FORMS.PP] ExceptionOccurred
Sender=EACCESSVIOLATION
Exception=Access violation
TApplication.HandleException Access violation
TApplication.HideAllFormsWithStayOnTop :TSPLASHFORM [FORMS.PP] ExceptionOccurred
[TgtkObject.Destroy] WARNING: There are 1 unreleased DCs, a detailed dump follows:
[TgtkObject.Destroy] DCs: 0858A614
[TgtkObject.Destroy] WARNING: There are 7 unreleased GDIObjects, a detailed dump follows:
[TgtkObject.Destroy] GDIOs: BF32F614 BF32F5C4 BF32F4E4 BF32F494 0858A6D4 BF17B004 BF3150B4
[TgtkObject.Destroy] gdiBitmap: 3
[TgtkObject.Destroy] gdiBrush: 1
[TgtkObject.Destroy] gdiFont: 2
[TgtkObject.Destroy] gdiPen: 1

with fpc-1.0.11 (runned for the 3rd time-funny even non workable message box appears)

[FORMS.PP] ExceptionOccurred
Sender=EACCESSVIOLATION
Exception=Access violation
TApplication.HandleException Access violation
TApplication.HideAllFormsWithStayOnTop :TSPLASHFORM [FORMS.PP] ExceptionOccurred
[TgtkObject.Destroy] WARNING: There are 1 unreleased DCs, a detailed dump follows:
[TgtkObject.Destroy] DCs: 0858A614
[TgtkObject.Destroy] WARNING: There are 7 unreleased GDIObjects, a detailed dump follows:
[TgtkObject.Destroy] GDIOs: BF32F614 BF32F5C4 BF32F4E4 BF32F494 0858A6D4 BF17B004 BF3150B4
[TgtkObject.Destroy] gdiBitmap: 3
[TgtkObject.Destroy] gdiBrush: 1
[TgtkObject.Destroy] gdiFont: 2
[TgtkObject.Destroy] gdiPen: 1

4th time no message box but exited for the first time

Yep, it reports that exception occured in exception if I remeber correctly

Later maybe, but as I stated, now that lazarus is not working. My notebook unfortunately stayed at home^^

I will send it later this day, is that some special option in gdb or something, I'm really not familiar with gdb in console mode, back when I was coding in c, at least until fpc and lazarus were usable I was always to lazy and used ddd

^^

Unfortunately exceptions aren't caught by gdb.

What you can do is setting a and
if it is hit, do a backtrace (bt)

You can set a breakpoint by
break TAPPLICATION__HANDLEEXCEPTION

then run.

If you hit the breakpoint do bt.

Marc

I haven't tried cvs but the rpms from the ccr site seem to work fine with Fedora 1.

http://sourceforge.net/project/showfiles.php?group_id=92177

fpc-1.0.11-031022.i386.rpm
fpcsrc-1.0.11-20031022.i386.rpm
lazarus-0.9.0.6-fpc_1.0.11_031022.i386.rpm

I'm planning to give cvs a try after I've had a chance to get the new install configured. Performance does seem to be much better then RH9.

-Tom

Just yesterday I installed Fedora and find it very surprising that for the first time in my life Lazarus doesn't work. It just throws out without even showing any Window, with exception "out of memory" to console

Sounds like an endless loop.

After that I tried with fpc 1.9, same result except MessageBox "Out of Memory" showed up.

Can you start it with gdb and send a backtrace?

Mattias