> Then please file a bug report with source code to reproduce the crash.
I'd love to but probably it only happens in my project with close to 500
units, it can be really hard to strip such things down. There is
unfortunately a lot of closed source code in it.
I will try installing FPC 2.5. Prob
On 10 Jul 2010, at 20:23, Tobias Giesen wrote:
> I manually deleted all .ppu, .o, and .rst files and it happens on a
> fresh build.
Then please file a bug report with source code to reproduce the crash.
> By the way could -Cs2000 do any harm? Maybe one 0 too many?
The stack size only affec
> > With FPC 2.4.0 I get Fatal: Compilation aborted: Unhandled exception
> > at ... on line 1 of some units.
>
> Does it still happen after cleaning the project and then rebuilding it?
I manually deleted all .ppu, .o, and .rst files and it happens on a
fresh build.
By the way could -Cs2000
On 10 Jul 2010, at 19:58, Tobias Giesen wrote:
> With FPC 2.4.0 I get Fatal: Compilation aborted: Unhandled exception
> at ... on line 1 of some units.
Does it still happen after cleaning the project and then rebuilding it?
Jonas
___
fpc-pascal mai
> Stabs or DWARF (-g or -gw)?
I think Stabs, but apparently it worked with Dwarf in one particular
installation. I will need to look into it more. Lazarus still says
"Oops, debugger error" so I need to find out how to look at the
communication between Lazarus and gbd to see the actual error.
Wit
On 10 Jul 2010, at 13:21, Tobias Giesen wrote:
> My compiled application with symbold is 93.5 MB in size and gdb cannot
> load it, so the debugger in Lazarus fails too.
Stabs or DWARF (-g or -gw)? I've seen this in the past with DWARF and
Lazarus-compiled applications, but never with Stabs.
>
Hello,
I am back developing for Mac!
My compiled application with symbold is 93.5 MB in size and gdb cannot
load it, so the debugger in Lazarus fails too.
This happens on both Leopard and Snow with FPC 2.2.x and 2.4.0 and
Lazarus 0.9.28 and 0.9.29.
Only the 2 year old installation on Tiger stil
