Florian Klaempfl wrote:
> Compile the IDE with GDB support (make clean all OPT=-g) run it inside GDB and
> post the stack trace:
>
> gdb ./fp
> r
> where
OK, I think it's reproducible. Simple program, to build and step, open
disassembly window, close and SEGV. First few lines of output, slightl
I have a program like below, and if the control variable (nr) is defined
as a byte/word it fails (the count goes from 1..14) But if I use an
Integer as control variable it works.
Is this an error in the compiler?
If I use the Windows compiler (fpc) it works.
Carsten
Florian Klaempfl wrote:
> Compile the IDE with GDB support (make clean all OPT=-g) run it inside GDB and
> post the stack trace:
>
> gdb ./fp
> r
> where
Ah- OK, I think I get that. Back in a few hours... :-)
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the auth
Tomas Hajny wrote:
> I guess that you could still use the cross-compilation trick - bring the
> library from the target machine to your build machine and change the
> search paths (probably manually - using "-s" option and playing with the
> generated script.res before running the created ppas.sh)
Mark Morgan Lloyd wrote:
The build worked and I appear to have an intact fpc and fp. However fp's
disassembly window is very fragile- SEGV at the drop of a hat.
I find I can't transfer the compiled bundle to another machine- I get "fp:
/lib/libc.so.6: version `GLIBC_2.3' not found (required by f
Mark Morgan Lloyd wrote:
> The build worked and I appear to have an intact fpc and fp. However fp's
> disassembly window is very fragile- SEGV at the drop of a hat.
>
> I find I can't transfer the compiled bundle to another machine- I get "fp:
> /lib/libc.so.6: version `GLIBC_2.3' not found (requir