Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2005-01

Lazarus problems with current FPC 1.9.7

4 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mattias Gaertner

Since a week I get strange, sporadic errors with current fpc. For example:

TMainIDE.DoSaveAll

Program received signal SIGSEGV, Segmentation fault. $0a9a0c08 in ?? ()
(gdb) bt
#0 $0a9a0c08 in ?? ()
First symbol in segment of executable not a source symbol

That's why I think, it's a compiler bug.

I get strange string bug. For example strings containing values of other strings.
With memcheck I can't reproduce it and see no bugs.

Also, saving xml files is much slower.
Any ideas, how I can help you to find the bug?

Mattias

Reply by email

Vincent Snijders
to Mattias Gaertner
Mattias Gaertner wrote 19 lines
Since a week I get strange, sporadic errors with current fpc. For example: TMainIDE.DoSaveAll Program received signal SIGSEGV, Segmentation fault. $0a9a0c08 in ?? () (gdb) bt #0 $0a9a0c08 in ?? () First symbol in segment of executable not a source symbol That's why I think, it's a compiler bug. I get strange string bug. For example strings containing values of other strings. With memcheck I can't reproduce it and see no bugs. Also, saving xml files is much slower. Any ideas, how I can help you to find the bug?

Another maybe related problem. If I make cycle on windows with starting compiler from fpc 1.0.10, ppc1 is wrong/corrupt and can't even produce a version number: ppc1 -iV exits with a stackdump.

Vincent

Reply by email

Peter Vreman
to Mattias Gaertner: Since a week I get strange, sporadic errors with current fpc. For example:…
Show quoted text 19 lines
Since a week I get strange, sporadic errors with current fpc. For example: TMainIDE.DoSaveAll Program received signal SIGSEGV, Segmentation fault. $0a9a0c08 in ?? () (gdb) bt #0 $0a9a0c08 in ?? () First symbol in segment of executable not a source symbol That's why I think, it's a compiler bug. I get strange string bug. For example strings containing values of other strings. With memcheck I can't reproduce it and see no bugs. Also, saving xml files is much slower. Any ideas, how I can help you to find the bug?

I tried the SaveAll but got no crash.

You can try to run lazarus under Valgrind.

Reply by email

Peter Vreman
to Vincent Snijders: Another maybe related problem. If I make cycle on windows with starting compiler from fpc…
Show quoted text 24 lines
Mattias Gaertner wrote: > Since a week I get strange, sporadic errors with current fpc. > For example: > > TMainIDE.DoSaveAll > > Program received signal SIGSEGV, Segmentation fault. > $0a9a0c08 in ?? () > (gdb) bt > #0 $0a9a0c08 in ?? () > First symbol in segment of executable not a source symbol > > That's why I think, it's a compiler bug. > > I get strange string bug. For example strings containing values of other > strings. > With memcheck I can't reproduce it and see no bugs. > > Also, saving xml files is much slower. > Any ideas, how I can help you to find the bug? Another maybe related problem. If I make cycle on windows with starting compiler from fpc 1.0.10, ppc1 is wrong/corrupt and can't even produce a version number: ppc1 -iV exits with a stackdump.

I guess that one is related to the use of SysUtils in the compiler. It has no impact on the code produced the 1.9.7. In the mean time use 1.9.4 or 1.9.6 to bootstrap 1.9.7

Reply by email