[Lazarus] Lazarus crashing reproducibly on startup (64-bit Linux)
Mark Morgan Lloyd
markMLl.lazarus at telemetry.co.uk
Sun Mar 18 16:45:37 CET 2012
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/0.9.28.2/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?
--
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