Sign in Join

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

Mailing lists / fpc-pascal / 2012-08

FPC trunk seems to crash compiling Lazreport; was: Re: Lazreport compilation problems with FPC trunk

9 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

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

Reinier Olislagers

Thread from Lazarus list...

Perhaps some kind FPC dev could look at bug 2252 if this is an FPC trunk bug connected with generating stabs debug info instead of a Lazreport/Lazarus bug7

Thanks,
Reinier

Maxim Ganetsky wrote 13 lines
12.08.2012 20:12, Reinier Olislagers пишет: > On 12-8-2012 12:57, Reinier Olislagers wrote: >> Hi list, >> >> I reported problems compiling Lazreport with FPC trunk in bug 22527 >> >> I'm trying to look for the cause, but the output doesn't show much: >> Compiling lr_progr.pas >> ... >> C:\development\lazarus_fpctrunk\components\lazreport\source\lr_progr.pas(1,1) >> >> Fatal: Compilation aborted >>

<snip>

Show quoted text 42 lines
> Setting verbosity to -va and keeping the package options "generate debug > info" (-g) and line numbers (-gl) gives: > ... a lot of output... > lr_class.pas(11454,3) Note: Local variable "wValue" not used > lr_class.pas(21,52) Hint: Unit "LMessages" not used in LR_Class > Searching file lr_dbset.pas... found > Searching file lr_utils.pas... found > Searching file lr_dbrel.pas... found > Searching file lr_view.pas... found > Searching file lr_barc.pas... found > Fatal: Compilation aborted > An unhandled exception occurred at $00403FF9: > EStackOverflow: Stack overflow > $00403FF9 line 410 of ../inc/sstrings.inc > $005858F2 line 372 of dbgstabs.pas > $0058852D line 1077 of dbgstabs.pas > $00442D7B line 595 of dbgbase.pas > $005307EA line 1095 of pmodules.pas > $004335DA line 395 of parser.pas > $00528318 line 1671 of fppu.pas > $0052F35B line 483 of pmodules.pas > $0052F521 line 545 of pmodules.pas > $004335DA line 395 of parser.pas > $00528318 line 1671 of fppu.pas > $0052F35B line 483 of pmodules.pas > $0052FF09 line 862 of pmodules.pas > $004335DA line 395 of parser.pas > $00528318 line 1671 of fppu.pas > $0052F35B line 483 of pmodules.pas > $0052F521 line 545 of pmodules.pas > > Error: C:\development\fpctrunk\bin\i386-win32\ppc386.exe returned an > error exitcode > > Hmmm? dbgstabs.pas suggests something to do with generating debug info > perhaps? > > -va and no -g -gl does let Lazarus compile the package. > > Perhaps the problem lies with the compiler instead of Lazreport? Yes it is, compiler shouldn't crash.

Reply by email

Jonas Maebe
to Reinier Olislagers
Reinier Olislagers wrote 5 lines
Thread from Lazarus list... Perhaps some kind FPC dev could look at bug 2252 if this is an FPC trunk bug connected with generating stabs debug info instead of a Lazreport/Lazarus bug7

I would suggest to start by not compiling the compiler or RTL with stack checking enabled.

Jonas

Reply by email

Ludo Brands
to Jonas Maebe
I would suggest to start by not compiling the compiler or RTL with stack checking enabled.

Is stack checking on by default? I encounter the same problem as Reinier and I build the compiler with OPT="-g -gl", nothing more.

Ludo

Reply by email

Jonas Maebe
to Ludo Brands
Ludo Brands wrote 5 lines
> I would suggest to start by not compiling the compiler or RTL > with stack checking enabled. > Is stack checking on by default?

No, it's not.

I encounter the same problem as Reinier and I build the compiler with OPT="-g -gl", nothing more.

Then it's probably something else.

Jonas

Reply by email

Reinier Olislagers
to Jonas Maebe
Jonas Maebe wrote 13 lines
On 12 Aug 2012, at 20:14, Ludo Brands wrote: >> I would suggest to start by not compiling the compiler or RTL >> with stack checking enabled. >> > > Is stack checking on by default? No, it's not. > I encounter the same problem as Reinier and > I build the compiler with OPT="-g -gl", nothing more.

Was just building again to confirm. Same as Ludo, OPT="-g -gl"... FPC x86 r22066, Win Vista x64 (also had problems with FPC x64) Lazarus trunk (but the lazreport problem has been going on for a while now)

Then it's probably something else.

Yes.

Reply by email

Reinier Olislagers
to Ludo Brands
Ludo Brands wrote 8 lines
>> I encounter the same problem as Reinier and >> I build the compiler with OPT="-g -gl", nothing more. > > Then it's probably something else. > Problem is caused by the changes in rev 21972. Code iterates now indefinitely TDebugInfoStabs.field_write_defs, TDebugInfo.appenddef, TDebugInfoStabs.beforeappenddef,...

Jonas,

Perhaps you might want to assign this bug to yourself given you're the author of 21972?
http://bugs.freepascal.org/view.php?id=22527

Thanks,
Reinier

Reply by email

Reinier Olislagers
to Jonas Maebe
Jonas Maebe wrote 10 lines
On 19 Aug 2012, at 17:25, Reinier Olislagers wrote: > Perhaps you might want to assign this bug to yourself given you're > the author of 21972? http://bugs.freepascal.org/view.php?id=22527 I can't, because I don't have admin access to Lazarus issues. Furthermore, I'd really appreciate a way to reproduce it without depending on Lazarus (or at least instructions on how to reproduce it from the command line, because always debug using plain gdb).

I understand. As mentioned in the issue, I think Somebody should reassign the issue to fpc at least anyway (which I can't do either).

No idea if this bug occurs in other code as well.

The way I found out is by running fpcup:
https://bitbucket.org/reiniero/fpcup/downloads/fpcup.exe

fpcup --fpcurl=http://svn.freepascal.org/svn/fpc/trunk --fpcopt="-gw -gl" --lazopt="-gw -gl"
Which you can run out of the box if you have svn.exe in your path (and nothing you want to keep in your c:\development\lazarus, c:\development\fpc, c:\development\fpcbootstrap and c:\development\extras directories)

After having run this once, you can dramatically shorten testing by: fpcup --fpcurl=http://svn.freepascal.org/svn/fpc/trunk --fpcopt="-gw -gl" --lazopt="-gw -gl" --only=useride

I can also look into writing up some instructions on runnning the svn update, make etc commands that fpcup sends out manually.

Thanks,
Reinier

Reply by email