[Lazarus] Lazarus crashing reproducibly on startup (64-bit Linux)

Mark Morgan Lloyd markMLl.lazarus at telemetry.co.uk
Mon Mar 19 18:13:11 CET 2012

brian wrote:
> On 03/18/2012 11:45 AM, Mark Morgan Lloyd wrote:
>> brian wrote:
>>> I've recently switched distros to Mint Debian 12 64-bit XFCE. This
>>> is on an AMD Phenom *4, 4 GB of RAM. When I was reinstalling stuff I
>>> noticed that the latest version of Lazarus that they have in the
>>> repo is 0.9.28, a bit old I know, but it works for what I do.
>>> So I installed 0.9.28, which also brought in FPC 2.4.0-2.
>>> When I try to run Lazarus from the menus, I get the splash screen
>>> and then nothing, the IDE never comes up.
>>> So, I switched to a terminal, ran startlazarus and got the following
>>> output.
>>> [WARNING] Out of OEM specific VK codes, changing to unassigned
>>> [WARNING] Out of unassigned VK codes, assigning $FF
>>> TLazarusManager.Run starting /usr/lib/lazarus/ ...
>>> Runtime error 203 at $0000000000736A16
>>> $0000000000736A16
>>> $0000000000720991
>>> OK, maybe it's an old version. I downloaded the latest .DEBs from
>>> SourceForge, and installed those. No change in the symptoms (well,
>>> OK, I can't say the addresses were exactly the same, but the bit
>>> about the VK codes was, and it was still a runtime error 203).
>>> I cleaned out everything to do with Lazarus and FPC that I could
>>> find (using KFind to make sure I got everything) and had one more
>>> try with 0.9.28. As expected, still the same error. I know that
>>> 0.9.28 used to run on Mint 9 64-bit, but that was the Ubuntu-based
>>> version, not the Debian-based one.
>>> Anyone have any ideas how to fix this, please?
>> Starting at a shell prompt, if you load Lazarus in gdb, run it, wait
>> for the crash and then use GDB's bt command to get a backtrace, do the
>> first few lines say anything useful?
> Probably not, but this is what was produced using V0.9.28
> <paste>
> run
> Starting program: /usr/bin/startlazarus
> [Thread debugging using libthread_db enabled]
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000000005a2879 in ?? ()
> (gdb) bt
> #0  0x00000000005a2879 in ?? ()
> #1  0x00007fffffffe1c0 in ?? ()
> #2  0x00007ffff7de902c in ?? () from /lib64/ld-linux-x86-64.so.2
> #3  0x0000000000502b31 in ?? ()
> #4  0x00007ffff577dead in __libc_start_main () from 
> /lib/x86_64-linux-gnu/libc.so.6
> #5  0x0000000000000000 in ?? ()
> (gdb)

I use Debian rather than Ubuntu, don't have x64, and generally build 
both FPC and Lazarus from source.

Put another way, I hope there's somebody active in the the list who's 
rather more au fait with your actual configuration than I am

Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]

More information about the Lazarus mailing list