Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Roland Turcan - RoTurSoft
Hello FPC-Pascal users discussions!

Compilation shows me next ugly error messages during building
lazarus with our components.

How can I turn on move verbose outputs to see more about the problem.

The strangest is, the same source code is buildable into Lazarus/Linux
without any problem, but Linux runs on i386 and MacOS on PPC. I guess
it is problem with compiler.

...
Assembling resconf
An unhandled exception occurred at $00148A30 :
EAccessViolation : Access violation
  $00148A30
  $001479D4
  $0014C90C
  $0014B05C
  $001245C0
  $0014FE78
  $00150378
  $0013321C
  $0012B980
  $00109044
  $0011D3C4
  $0012AAEC
  $0012AE00
  $0012BB88
  $00Fatal: Compilation aborted
109044
  $0011D3C4
  $0012AAEC

TExternalToolList.Run Exception: there was an error
ERROR: tool reported error


Thanks.

--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
On Tue, 22 Jul 2008 11:02:40 +0200
Roland Turcan <[hidden email]> wrote:

> Hello FPC-Pascal users discussions!
>
> Compilation shows me next ugly error messages during building
> lazarus with our components.
>
> How can I turn on move verbose outputs to see more about the problem.
>
> The strangest is, the same source code is buildable into Lazarus/Linux
> without any problem, but Linux runs on i386 and MacOS on PPC. I guess
> it is problem with compiler.
>
> ...
> Assembling resconf
> An unhandled exception occurred at $00148A30 :
> EAccessViolation : Access violation
>   $00148A30
>   $001479D4
>   $0014C90C
>   $0014B05C
>   $001245C0
>   $0014FE78
>   $00150378
>   $0013321C
>   $0012B980
>   $00109044
>   $0011D3C4
>   $0012AAEC
>   $0012AE00
>   $0012BB88
>   $00Fatal: Compilation aborted
> 109044
>   $0011D3C4
>   $0012AAEC
>
> TExternalToolList.Run Exception: there was an error
> ERROR: tool reported error

Start lazarus in gdb, reproduce the problem and create a backtrace.

http://wiki.lazarus.freepascal.org/Creating_a_Backtrace_with_GDB#Linux.2FBSD_Users.2FMacOSX

Mattias
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Vincent Snijders
In reply to this post by Roland Turcan - RoTurSoft
Roland Turcan schreef:

> Hello FPC-Pascal users discussions!
>
> Compilation shows me next ugly error messages during building
> lazarus with our components.
>
> How can I turn on move verbose outputs to see more about the problem.
>
> The strangest is, the same source code is buildable into Lazarus/Linux
> without any problem, but Linux runs on i386 and MacOS on PPC. I guess
> it is problem with compiler.
>

If this is a compiler bug, try compiling the compiler with -gl to show line number
information about the compiler crash. Usually this doesn't help me much tough,
because I cannot fix the compiler. In such cases, I try to create a bug report with
a small example that shows the crash.

Maybe compiling lazarus with -vl shows where the compilation process halts.

Vincent
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
On Tue, 22 Jul 2008 11:33:30 +0200
Vincent Snijders <[hidden email]> wrote:

> Roland Turcan schreef:
> > Hello FPC-Pascal users discussions!
> >
> > Compilation shows me next ugly error messages during building
> > lazarus with our components.
> >
> > How can I turn on move verbose outputs to see more about the
> > problem.
> >
> > The strangest is, the same source code is buildable into
> > Lazarus/Linux without any problem, but Linux runs on i386 and MacOS
> > on PPC. I guess it is problem with compiler.
> >
>
> If this is a compiler bug, try compiling the compiler with -gl to
> show line number information about the compiler crash. Usually this
> doesn't help me much tough, because I cannot fix the compiler. In
> such cases, I try to create a bug report with a small example that
> shows the crash.
>
> Maybe compiling lazarus with -vl shows where the compilation process
> halts.

The Lineinfo unit does not work currently under Mac OS X.
gdb works.

Mattias
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Jonas Maebe-2

On 22 Jul 2008, at 11:13, Mattias Gaertner wrote:

> The Lineinfo unit does not work currently under Mac OS X.

The lineinfo unit does work under Mac OS X (but only for stabs  
currently). Depending on the used system version, it may also only  
work if you start the program with the full path, because paramstr(0)  
is not guaranteed to contain the full path to the binary (as for why,  
see http://lists.apple.com/archives/darwin-kernel/2004/Jul/ 
msg00058.html ; and note that those arguments hold equally well for  
any *nix, so in general it's a bad idea to rely on paramstr(0) being a  
valid full path to some existing file).


Jonas
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
Zitat von Jonas Maebe <[hidden email]>:

>
> On 22 Jul 2008, at 11:13, Mattias Gaertner wrote:
>
> > The Lineinfo unit does not work currently under Mac OS X.
>
> The lineinfo unit does work under Mac OS X (but only for stabs
> currently).

Ah.

This means: either lineinfo and a lot of linker warnings on each compile XOR no
lineinfo and no warnings, right?

dwarf is the future, isn't it?
What is needed to get lineinfo working with dwarf?


> Depending on the used system version, it may also only
> work if you start the program with the full path, because paramstr(0)
> is not guaranteed to contain the full path to the binary (as for why,
> see http://lists.apple.com/archives/darwin-kernel/2004/Jul/
> msg00058.html ; and note that those arguments hold equally well for
> any *nix, so in general it's a bad idea to rely on paramstr(0) being a
> valid full path to some existing file).


Mattias

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Jonas Maebe-2

On 22 Jul 2008, at 12:43, Mattias Gärtner wrote:

> This means: either lineinfo and a lot of linker warnings on each  
> compile XOR no
> lineinfo and no warnings, right?

If you don't use the patched linker, yes.

> dwarf is the future, isn't it?
> What is needed to get lineinfo working with dwarf?

Support for
a) finding the original object files used to link the program (the  
paths are probably stored in the binary when you use dwarf) and  
reading the dwarf info from them
and/or
b) finding the dsym bundle and reading the dwarf info from that one  
(if you compiled with -Xg)


Jonas_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re[2]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Roland Turcan - RoTurSoft
In reply to this post by Mattias Gaertner
Hello all,

Backtrace from lazbuild:

An unhandled exception occurred at $00148A30 :

Breakpoint 1, 0x00018090 in fpc_raiseexception ()
(gdb) bt
#0  0x00018090 in fpc_raiseexception ()
#1  0x001106d4 in CHECKFORURGENTMESSAGES (P=1, parentfp=0xbfffe0c0) at outputfilter.pas:561
#2  0x0010e400 in TOUTPUTFILTER__READFPCOMPILERLINE (S=0x3129048, this=0x27002a0)
#3  0x0010e0b8 in TOUTPUTFILTER__READLINE (S=0x3129048, DONTFILTERLINE=false, this=0x27002a0) at outputfilter.pas:418
#4  0x0010dbcc in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20, ACALLER=0x25ded00, ATOOL=0x27c3ac0, this=0x27002a0)
#5  0x003b7c1c in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x27c3ac0, MACROS=0x27aa200, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90, this=0x25ded00) at exttooldialog.pas:370
#6  0x0017eb88 in TBUILDMANAGER__ONRUNCOMPILERWITHOPTIONS (EXTTOOL=0x27c3ac0, COMPOPTIONS=0x27f4e90, this=0x25cd860) at buildmanager.pas:1221
#7  0x0016e004 in TLAZPACKAGEGRAPH__COMPILEPACKAGE (APACKAGE=0x3148b80, FLAGS=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2935
#8  0x0016d600 in TLAZPACKAGEGRAPH__COMPILEREQUIREDPACKAGES (APACKAGE=0x0, FIRSTDEPENDENCY=0x3156f60, GLOBALS=0x31070e0, POLICIES=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2766
#9  0x00003fac in TLAZBUILDAPPLICATION__COMPILEAUTOINSTALLPACKAGES (this=0x2730090) at lazbuild.lpr:502
#10 0x00003c68 in TLAZBUILDAPPLICATION__BUILDLAZARUSIDE (this=0x2730090) at lazbuild.lpr:445
#11 0x000067fc in TLAZBUILDAPPLICATION__RUN (this=0x2730090) at lazbuild.lpr:978
#12 0x00007f48 in PASCALMAIN () at lazbuild.lpr:1167
#13 0x0002a980 in SYSTEM_FPC_SYSTEMMAIN$LONGINT$PPCHAR$PPCHAR ()
#14 0x000026fc in _start ()
#15 0x00002400 in start ()


I wanted to make the backtrace from lazarus too, but when I run
lazarus from terminal then terminal's menu is shown instead of
lazarus' one.


Thanks.

TRoland;


<<< 22.7.2008 11:28 - Mattias Gaertner "[hidden email]" >>>
MG> On Tue, 22 Jul 2008 11:02:40 +0200
MG> Roland Turcan <[hidden email]> wrote:

>> Hello FPC-Pascal users discussions!
>>
>> Compilation shows me next ugly error messages during building
>> lazarus with our components.
>>
>> How can I turn on move verbose outputs to see more about the problem.
>>
>> The strangest is, the same source code is buildable into Lazarus/Linux
>> without any problem, but Linux runs on i386 and MacOS on PPC. I guess
>> it is problem with compiler.
>>
>> ...
>> Assembling resconf
>> An unhandled exception occurred at $00148A30 :
>> EAccessViolation : Access violation
>>   $00148A30
>>   $001479D4
>>   $0014C90C
>>   $0014B05C
>>   $001245C0
>>   $0014FE78
>>   $00150378
>>   $0013321C
>>   $0012B980
>>   $00109044
>>   $0011D3C4
>>   $0012AAEC
>>   $0012AE00
>>   $0012BB88
>>   $00Fatal: Compilation aborted
>> 109044
>>   $0011D3C4
>>   $0012AAEC
>>
>> TExternalToolList.Run Exception: there was an error
>> ERROR: tool reported error

MG> Start lazarus in gdb, reproduce the problem and create a backtrace.

MG> http://wiki.lazarus.freepascal.org/Creating_a_Backtrace_with_GDB#Linux.2FBSD_Users.2FMacOSX

MG> Mattias




--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Re[2]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Jonas Maebe-2

On 22 Jul 2008, at 13:29, Roland Turcan wrote:

> I wanted to make the backtrace from lazarus too, but when I run
> lazarus from terminal then terminal's menu is shown instead of
> lazarus' one.

If you use

gdb lazarus.app

it should work fine.


Jonas
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Re[2]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
In reply to this post by Roland Turcan - RoTurSoft
Zitat von Roland Turcan <[hidden email]>:

> Hello all,
>
> Backtrace from lazbuild:
>
> An unhandled exception occurred at $00148A30 :
>
> Breakpoint 1, 0x00018090 in fpc_raiseexception ()
> (gdb) bt
> #0  0x00018090 in fpc_raiseexception ()
> #1  0x001106d4 in CHECKFORURGENTMESSAGES (P=1, parentfp=0xbfffe0c0) at
> outputfilter.pas:561
> #2  0x0010e400 in TOUTPUTFILTER__READFPCOMPILERLINE (S=0x3129048,
> this=0x27002a0)
> #3  0x0010e0b8 in TOUTPUTFILTER__READLINE (S=0x3129048, DONTFILTERLINE=false,
> this=0x27002a0) at outputfilter.pas:418
> #4  0x0010dbcc in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20,
> ACALLER=0x25ded00, ATOOL=0x27c3ac0, this=0x27002a0)
> #5  0x003b7c1c in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x27c3ac0,
> MACROS=0x27aa200, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90,
> this=0x25ded00) at exttooldialog.pas:370
>[...]

This exception is normal and caught in ide/exttooldialog.pas 387.
Please continue and see what comes next:

gdb ./lazarus.app/Contents/MacOS/lazarus
break FPC_RAISEEXCEPTION
r
bt
c
bt
c
bt


Mattias

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re[4]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Roland Turcan - RoTurSoft
Hello Mattias,

Next backtrace:

Compiling ./unit/ResConf.pas
Assembling resconf
An unhandled exception occurred at $00148A20 :

Breakpoint 1, 0x00018100 in fpc_raiseexception ()
(gdb) bt
#0  0x00018100 in fpc_raiseexception ()
#1  0x0010dde4 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20, ACALLER=0x25ded00, ATOOL=0x27c3d90, this=0x27002a0)
#2  0x003b7bac in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x27c3d90, MACROS=0x27aa800, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90, this=0x25ded00) at exttooldialog.pas:370
#3  0x0017ebb8 in TBUILDMANAGER__ONRUNCOMPILERWITHOPTIONS (EXTTOOL=0x27c3d90, COMPOPTIONS=0x27f4e90, this=0x25cd860) at buildmanager.pas:1221
#4  0x0016e034 in TLAZPACKAGEGRAPH__COMPILEPACKAGE (APACKAGE=0x3148b80, FLAGS=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2935
#5  0x0016d630 in TLAZPACKAGEGRAPH__COMPILEREQUIREDPACKAGES (APACKAGE=0x0, FIRSTDEPENDENCY=0x3156f60, GLOBALS=0x3107130, POLICIES=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2766
#6  0x0000401c in TLAZBUILDAPPLICATION__COMPILEAUTOINSTALLPACKAGES (this=0x2730090) at lazbuild.lpr:502
#7  0x00003cd8 in TLAZBUILDAPPLICATION__BUILDLAZARUSIDE (this=0x2730090) at lazbuild.lpr:445
#8  0x0000686c in TLAZBUILDAPPLICATION__RUN (this=0x2730090) at lazbuild.lpr:978
#9  0x00007fb8 in PASCALMAIN () at lazbuild.lpr:1167
#10 0x0002a9f0 in SYSTEM_FPC_SYSTEMMAIN$LONGINT$PPCHAR$PPCHAR ()
#11 0x0000276c in _start ()
#12 0x00002470 in start ()
(gdb) c
Continuing.
EAccessViolation : Access violation
  $00148A20
  $001479C4
  $0014C8FC
  $0014B04C
  $001245B0
  $0014FE68
  $00150368
  $0013320C
  $0012B970
  $00109034
  $0011D3B4
  $0012AADC
  $0012ADF0
  $0012BB78
  $00Fatal: Compilation aborted
109034
  $0011D3B4
  $0012AADC

TExternalToolList.Run Exception: there was an error
ERROR: tool reported error

Program exited with code 02.
(gdb)


But I don't see any debug information from freepascal's executable.

This is really strange, because our package is compilable alone
without problem.

TRoland;

<<< 22.7.2008 15:27 - Mattias Gärtner "[hidden email]" >>>
MG> Zitat von Roland Turcan <[hidden email]>:

>> Hello all,
>>
>> Backtrace from lazbuild:
>>
>> An unhandled exception occurred at $00148A30 :
>>
>> Breakpoint 1, 0x00018090 in fpc_raiseexception ()
>> (gdb) bt
>> #0  0x00018090 in fpc_raiseexception ()
>> #1  0x001106d4 in CHECKFORURGENTMESSAGES (P=1, parentfp=0xbfffe0c0) at
>> outputfilter.pas:561
>> #2  0x0010e400 in TOUTPUTFILTER__READFPCOMPILERLINE (S=0x3129048,
>> this=0x27002a0)
>> #3  0x0010e0b8 in TOUTPUTFILTER__READLINE (S=0x3129048, DONTFILTERLINE=false,
>> this=0x27002a0) at outputfilter.pas:418
>> #4  0x0010dbcc in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20,
>> ACALLER=0x25ded00, ATOOL=0x27c3ac0, this=0x27002a0)
>> #5  0x003b7c1c in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x27c3ac0,
>> MACROS=0x27aa200, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90,
>> this=0x25ded00) at exttooldialog.pas:370
>>[...]

MG> This exception is normal and caught in ide/exttooldialog.pas 387.
MG> Please continue and see what comes next:

MG> gdb ./lazarus.app/Contents/MacOS/lazarus
MG> break FPC_RAISEEXCEPTION
MG> r
MG> bt
MG> c
MG> bt
MG> c
MG> bt


MG> Mattias

MG> _______________________________________________
MG> fpc-pascal maillist  -  [hidden email]
MG> http://lists.freepascal.org/mailman/listinfo/fpc-pascal




--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Re[4]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
Zitat von Roland Turcan <[hidden email]>:

> Hello Mattias,
>
> Next backtrace:
>
> Compiling ./unit/ResConf.pas
> Assembling resconf
> An unhandled exception occurred at $00148A20 :
>
> Breakpoint 1, 0x00018100 in fpc_raiseexception ()
> (gdb) bt
> #0  0x00018100 in fpc_raiseexception ()
> #1  0x0010dde4 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20,
> ACALLER=0x25ded00, ATOOL=0x27c3d90, this=0x27002a0)

no line number. :(

> #2  0x003b7bac in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x27c3d90,
> MACROS=0x27aa800, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90,
> this=0x25ded00) at exttooldialog.pas:370
> #3  0x0017ebb8 in TBUILDMANAGER__ONRUNCOMPILERWITHOPTIONS (EXTTOOL=0x27c3d90,
> COMPOPTIONS=0x27f4e90, this=0x25cd860) at buildmanager.pas:1221
>[...]
> (gdb) c
> Continuing.
> EAccessViolation : Access violation
>[...]
> Fatal: Compilation aborted
>
> 109034
>   $0011D3B4
>   $0012AADC
>
> TExternalToolList.Run Exception: there was an error
> ERROR: tool reported error

This line should only appear, if the Exception is an EOutputFilterError, not on
EAccessViolation. Strange.
I will do some tests tonight on a Mac.


> Program exited with code 02.
> (gdb)
>
>
> But I don't see any debug information from freepascal's executable.
>
> This is really strange, because our package is compilable alone
> without problem.

Indeed.

Mattias

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Re[4]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
In reply to this post by Roland Turcan - RoTurSoft
Zitat von Roland Turcan <[hidden email]>:

> Hello Mattias,
>
> Next backtrace:
>
> Compiling ./unit/ResConf.pas
> Assembling resconf
> An unhandled exception occurred at $00148A20 :
>
> Breakpoint 1, 0x00018100 in fpc_raiseexception ()
> (gdb) bt
> #0  0x00018100 in fpc_raiseexception ()
> #1  0x0010dde4 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20,
> ACALLER=0x25ded00, ATOOL=0x27c3d90, this=0x27002a0)
> #2  0x003b7bac in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x27c3d90,
> MACROS=0x27aa800, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90,
> this=0x25ded00) at exttooldialog.pas:370

I think the AV happens somewhere in the finally part of ide/outputfilter.pas
375.
I added some verbosity in rev 15849.
Please update lazarus svn and compile IDE and lazbuild clean with
-dVerboseOFExecute.
Then try again.

Can you reproduce the bug in a smaller package and send me the example?

Mattias

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re[6]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Roland Turcan - RoTurSoft
Hello Mattias,

MG> I think the AV happens somewhere in the finally part of ide/outputfilter.pas
MG> 375.
MG> I added some verbosity in rev 15849.
MG> Please update lazarus svn and compile IDE and lazbuild clean with
MG> -dVerboseOFExecute.
MG> Then try again.

I have tried this:

(gdb) run
Starting program: /usr/local/share/lazarus/lazbuild --build-ide=-dVerboseOFExecute

and also this

(gdb) run
Starting program: /usr/local/share/lazarus/lazbuild --build-ide=-va-dVerboseOFExecute

but the result doesn't have more information:

Compiling ./unit/ResConf.pas
Assembling resconf
An unhandled exception occurred at $00148A20 :

Breakpoint 1, 0x000174c0 in fpc_raiseexception ()
(gdb) bt
#0  0x000174c0 in fpc_raiseexception ()
#1  0x0010d1e4 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20, ACALLER=0x25e0d20, ATOOL=0x3113230, this=0x27002a0)
#2  0x003b736c in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x3113230, MACROS=0x27aaae0, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90, this=0x25e0d20) at exttooldialog.pas:370
#3  0x0017dfd8 in TBUILDMANAGER__ONRUNCOMPILERWITHOPTIONS (EXTTOOL=0x3113230, COMPOPTIONS=0x27f4e90, this=0x25cf890) at buildmanager.pas:1221
#4  0x0016d454 in TLAZPACKAGEGRAPH__COMPILEPACKAGE (APACKAGE=0x3148b80, FLAGS=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2935
#5  0x0016ca50 in TLAZPACKAGEGRAPH__COMPILEREQUIREDPACKAGES (APACKAGE=0x0, FIRSTDEPENDENCY=0x31570f0, GLOBALS=0x310f150, POLICIES=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2766
#6  0x000033dc in TLAZBUILDAPPLICATION__COMPILEAUTOINSTALLPACKAGES (this=0x2730090) at lazbuild.lpr:502
#7  0x00003098 in TLAZBUILDAPPLICATION__BUILDLAZARUSIDE (this=0x2730090) at lazbuild.lpr:445
#8  0x00005c2c in TLAZBUILDAPPLICATION__RUN (this=0x2730090) at lazbuild.lpr:978
#9  0x00007378 in PASCALMAIN () at lazbuild.lpr:1167
#10 0x00029db0 in SYSTEM_FPC_SYSTEMMAIN$LONGINT$PPCHAR$PPCHAR ()
#11 0x00001b2c in _start ()
#12 0x00001830 in start ()

What did I wrong?

MG> Can you reproduce the bug in a smaller package and send me the example?

Actually the package contains over 500 units, but when I/we find the
reason then I will make some.

PS: I am going to holiday and I will not reply to any email (no
computer, no Internet) until 4.8.

Thanks for everything you did for me.

TRoland;

<<< 23.7.2008 17:02 - Mattias Gärtner "[hidden email]" >>>
MG> Zitat von Roland Turcan <[hidden email]>:

>> Hello Mattias,
>>
>> Next backtrace:
>>
>> Compiling ./unit/ResConf.pas
>> Assembling resconf
>> An unhandled exception occurred at $00148A20 :
>>
>> Breakpoint 1, 0x00018100 in fpc_raiseexception ()
>> (gdb) bt
>> #0  0x00018100 in fpc_raiseexception ()
>> #1  0x0010dde4 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2700a20,
>> ACALLER=0x25ded00, ATOOL=0x27c3d90, this=0x27002a0)
>> #2  0x003b7bac in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x27c3d90,
>> MACROS=0x27aa800, THEOUTPUTFILTER=0x27002a0, COMPILEROPTIONS=0x27f4e90,
>> this=0x25ded00) at exttooldialog.pas:370

MG> I think the AV happens somewhere in the finally part of ide/outputfilter.pas
MG> 375.
MG> I added some verbosity in rev 15849.
MG> Please update lazarus svn and compile IDE and lazbuild clean with
MG> -dVerboseOFExecute.
MG> Then try again.

MG> Can you reproduce the bug in a smaller package and send me the example?

MG> Mattias

MG> _______________________________________________
MG> fpc-pascal maillist  -  [hidden email]
MG> http://lists.freepascal.org/mailman/listinfo/fpc-pascal




--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
On Thu, 24 Jul 2008 23:58:45 +0200
Roland Turcan <[hidden email]> wrote:

> Hello Mattias,
>
> MG> I think the AV happens somewhere in the finally part of
> MG> ide/outputfilter.pas 375.
> MG> I added some verbosity in rev 15849.
> MG> Please update lazarus svn and compile IDE and lazbuild clean with
> MG> -dVerboseOFExecute.
> MG> Then try again.
>
> I have tried this:
>
> (gdb) run
> Starting program: /usr/local/share/lazarus/lazbuild
> --build-ide=-dVerboseOFExecute

Sorry. A misunderstanding.
You need to update lazarus svn and rebuild lazbuild itself, before
trying to use lazbuild to build your package. Which means:

cd /usr/local/share/lazarus
svn up
make clean all lazbuilder
./lazbuild --build-ide=-va > all_output.txt

 
> and also this
>
> (gdb) run
> Starting program: /usr/local/share/lazarus/lazbuild
> --build-ide=-va-dVerboseOFExecute

Note: Multiple parameters must be separated by space:

/usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"

 
>[...]

Mattias
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re[2]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Roland Turcan - RoTurSoft
Hello Mattias,

MG> /usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"

I have done all things you wrote me, but the result of compilation
didn't write any line written by WriteLn inside of IFDEFs. Maybe there
could be a bug during parsing of -d parameter and IFDEF sections were
not compiled into the code. Therefore I have commented IFDEFs out to
get them into lazbuild and the result is the following:

Compiling ./unit/ResConf.pas
Assembling resconf
An unhandled exception occurred at $00148A20 :
TOutputFilter.Execute W1
TOutputFilter.Execute W2
EAccessViolation : Access violation
  $00148A20
  $001479C4
  $0014C8FC
  $0014B04C
  $001245B0
  $0014FE68
  $00150368
  $0013320C
  $0012B970
  $00109034
  $0011D3B4
  $0012AADC
  $0012ADF0
  $0012BB78
  $00Fatal: Compilation aborted
109034
  $0011D3B4
  $0012AADC

TOutputFilter.Execute W3
TOutputFilter.Execute W4
TOutputFilter.Execute W5
TOutputFilter.Execute W6
TOutputFilter.Execute W7
TExternalToolList.Run Exception: there was an error
ERROR: tool reported error

TRoland;


<<< 25.7.2008 0:45 - Mattias Gaertner "[hidden email]" >>>
MG> On Thu, 24 Jul 2008 23:58:45 +0200
MG> Roland Turcan <[hidden email]> wrote:

>> Hello Mattias,
>>
>> MG> I think the AV happens somewhere in the finally part of
>> MG> ide/outputfilter.pas 375.
>> MG> I added some verbosity in rev 15849.
>> MG> Please update lazarus svn and compile IDE and lazbuild clean with
>> MG> -dVerboseOFExecute.
>> MG> Then try again.
>>
>> I have tried this:
>>
>> (gdb) run
>> Starting program: /usr/local/share/lazarus/lazbuild
>> --build-ide=-dVerboseOFExecute

MG> Sorry. A misunderstanding.
MG> You need to update lazarus svn and rebuild lazbuild itself, before
MG> trying to use lazbuild to build your package. Which means:

MG> cd /usr/local/share/lazarus
MG> svn up
MG> make clean all lazbuilder
MG> ./lazbuild --build-ide=-va > all_output.txt

MG>  
>> and also this
>>
>> (gdb) run
>> Starting program: /usr/local/share/lazarus/lazbuild
>> --build-ide=-va-dVerboseOFExecute

MG> Note: Multiple parameters must be separated by space:

MG> /usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"

MG>  
>>[...]

MG> Mattias




--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re[3]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Roland Turcan - RoTurSoft
Hello Mattias,

I have forgotten to send also result of building under gdb. Here is:

Compiling ./unit/ResConf.pas
Assembling resconf
An unhandled exception occurred at $00148A20 :

Breakpoint 1, 0x00017500 in fpc_raiseexception ()
(gdb) bt
#0  0x00017500 in fpc_raiseexception ()
#1  0x0010d334 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2788a20, ACALLER=0x25e9d40, ATOOL=0x2997200, this=0x27882a0)
#2  0x003b7bbc in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x2997200, MACROS=0x29780c0, THEOUTPUTFILTER=0x27882a0, COMPILEROPTIONS=0x297ce90, this=0x25e9d40) at exttooldialog.pas:370
#3  0x0017e458 in TBUILDMANAGER__ONRUNCOMPILERWITHOPTIONS (EXTTOOL=0x2997200, COMPOPTIONS=0x297ce90, this=0x25d8860) at buildmanager.pas:1222
#4  0x0016d804 in TLAZPACKAGEGRAPH__COMPILEPACKAGE (APACKAGE=0x29ccb80, FLAGS=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2947
#5  0x0016ce00 in TLAZPACKAGEGRAPH__COMPILEREQUIREDPACKAGES (APACKAGE=0x0, FIRSTDEPENDENCY=0x29db0a0, GLOBALS=0x25e66d0, POLICIES=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2778
#6  0x0000341c in TLAZBUILDAPPLICATION__COMPILEAUTOINSTALLPACKAGES (this=0x27b8090) at lazbuild.lpr:502
#7  0x000030d8 in TLAZBUILDAPPLICATION__BUILDLAZARUSIDE (this=0x27b8090) at lazbuild.lpr:445
#8  0x00005c6c in TLAZBUILDAPPLICATION__RUN (this=0x27b8090) at lazbuild.lpr:978
#9  0x000073b8 in PASCALMAIN () at lazbuild.lpr:1167
#10 0x00029df0 in SYSTEM_FPC_SYSTEMMAIN$LONGINT$PPCHAR$PPCHAR ()
#11 0x00001b6c in _start ()
#12 0x00001870 in start ()
(gdb) c
Continuing.
TOutputFilter.Execute W1
TOutputFilter.Execute W2
EAccessViolation : Access violation
  $00148A20
  $001479C4
  $0014C8FC
  $0014B04C
  $001245B0
  $0014FE68
  $00150368
  $0013320C
  $0012B970
  $00109034
  $0011D3B4
  $0012AADC
  $0012ADF0
  $0012BB78
TOutputFilter.Execute W3
TOutputFilter.Execute W4
TOutputFilter.Execute W5
TOutputFilter.Execute W6
TOutputFilter.Execute W7
TExternalToolList.Run Exception: there was an error
ERROR: tool reported error


TRoland;

<<< 4.8.2008 11:56 - Roland Turcan "[hidden email]" >>>
RT> Hello Mattias,

MG>> /usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"

RT> I have done all things you wrote me, but the result of compilation
RT> didn't write any line written by WriteLn inside of IFDEFs. Maybe there
RT> could be a bug during parsing of -d parameter and IFDEF sections were
RT> not compiled into the code. Therefore I have commented IFDEFs out to
RT> get them into lazbuild and the result is the following:

RT> Compiling ./unit/ResConf.pas
RT> Assembling resconf
RT> An unhandled exception occurred at $00148A20 :
RT> TOutputFilter.Execute W1
RT> TOutputFilter.Execute W2
RT> EAccessViolation : Access violation
RT>   $00148A20
RT>   $001479C4
RT>   $0014C8FC
RT>   $0014B04C
RT>   $001245B0
RT>   $0014FE68
RT>   $00150368
RT>   $0013320C
RT>   $0012B970
RT>   $00109034
RT>   $0011D3B4
RT>   $0012AADC
RT>   $0012ADF0
RT>   $0012BB78
RT>   $00Fatal: Compilation aborted
RT> 109034
RT>   $0011D3B4
RT>   $0012AADC

RT> TOutputFilter.Execute W3
RT> TOutputFilter.Execute W4
RT> TOutputFilter.Execute W5
RT> TOutputFilter.Execute W6
RT> TOutputFilter.Execute W7
RT> TExternalToolList.Run Exception: there was an error
RT> ERROR: tool reported error

RT> TRoland;


RT> <<< 25.7.2008 0:45 - Mattias Gaertner "[hidden email]" >>>
MG>> On Thu, 24 Jul 2008 23:58:45 +0200
MG>> Roland Turcan <[hidden email]> wrote:

>>> Hello Mattias,
>>>
>>> MG> I think the AV happens somewhere in the finally part of
>>> MG> ide/outputfilter.pas 375.
>>> MG> I added some verbosity in rev 15849.
>>> MG> Please update lazarus svn and compile IDE and lazbuild clean with
>>> MG> -dVerboseOFExecute.
>>> MG> Then try again.
>>>
>>> I have tried this:
>>>
>>> (gdb) run
>>> Starting program: /usr/local/share/lazarus/lazbuild
>>> --build-ide=-dVerboseOFExecute

MG>> Sorry. A misunderstanding.
MG>> You need to update lazarus svn and rebuild lazbuild itself, before
MG>> trying to use lazbuild to build your package. Which means:

MG>> cd /usr/local/share/lazarus
MG>> svn up
MG>> make clean all lazbuilder
MG>> ./lazbuild --build-ide=-va > all_output.txt

MG>>  
>>> and also this
>>>
>>> (gdb) run
>>> Starting program: /usr/local/share/lazarus/lazbuild
>>> --build-ide=-va-dVerboseOFExecute

MG>> Note: Multiple parameters must be separated by space:

MG>> /usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"

MG>>  
>>>[...]

MG>> Mattias








--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re[4]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Roland Turcan - RoTurSoft
Hello Mattias,

I have also uncommented some DebugLns which are inside of code:

Compiling ./unit/ResConf.pas
Assembling resconf
An unhandled exception occurred at $00148A20 :
TOutputFilter.Execute After Loop
TOutputFilter.Execute fProcess.ExitStatus=217

Breakpoint 1, 0x000173e0 in fpc_raiseexception ()
(gdb) bt
#0  0x000173e0 in fpc_raiseexception ()
#1  0x0010d33c in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2788a20, ACALLER=0x25e9d40, ATOOL=0x2c35340, this=0x27882a0)
#2  0x003b7bbc in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x2c35340, MACROS=0x29780c0, THEOUTPUTFILTER=0x27882a0, COMPILEROPTIONS=0x297ce90, this=0x25e9d40) at exttooldialog.pas:370
#3  0x0017e458 in TBUILDMANAGER__ONRUNCOMPILERWITHOPTIONS (EXTTOOL=0x2c35340, COMPOPTIONS=0x297ce90, this=0x25d8860) at buildmanager.pas:1222
#4  0x0016d804 in TLAZPACKAGEGRAPH__COMPILEPACKAGE (APACKAGE=0x29ccb80, FLAGS=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2947
#5  0x0016ce00 in TLAZPACKAGEGRAPH__COMPILEREQUIREDPACKAGES (APACKAGE=0x0, FIRSTDEPENDENCY=0x29db0a0, GLOBALS=0x25e66d0, POLICIES=Invalid C/C++ type code 10 in symbol table.
) at packagesystem.pas:2778
#6  0x000032fc in TLAZBUILDAPPLICATION__COMPILEAUTOINSTALLPACKAGES (this=0x27b8090) at lazbuild.lpr:502
#7  0x00002fb8 in TLAZBUILDAPPLICATION__BUILDLAZARUSIDE (this=0x27b8090) at lazbuild.lpr:445
#8  0x00005b4c in TLAZBUILDAPPLICATION__RUN (this=0x27b8090) at lazbuild.lpr:978
#9  0x00007298 in PASCALMAIN () at lazbuild.lpr:1167
#10 0x00029cd0 in SYSTEM_FPC_SYSTEMMAIN$LONGINT$PPCHAR$PPCHAR ()
#11 0x00001a4c in _start ()
#12 0x00001750 in start ()
(gdb) c
Continuing.
TOutputFilter.Execute W1
TOutputFilter.Execute W2
EAccessViolation : Access violation
  $00148A20
  $001479C4
  $0014C8FC
  $0014B04C
  $001245B0
  $0014FE68
  $00150368
  $0013320C
  $0012B970
  $00109034
  $0011D3B4
  $0012AADC
  $0012ADF0
  $0012BB78
TOutputFilter.Execute W3
TOutputFilter.Execute W4
TOutputFilter.Execute W5
TOutputFilter.Execute W6
TOutputFilter.Execute W7
TExternalToolList.Run Exception: there was an error
ERROR: tool reported error

Program exited with code 02.


<<< 4.8.2008 12:03 - Roland Turcan "[hidden email]" >>>
RT> Hello Mattias,

RT> I have forgotten to send also result of building under gdb. Here is:

RT> Compiling ./unit/ResConf.pas
RT> Assembling resconf
RT> An unhandled exception occurred at $00148A20 :

RT> Breakpoint 1, 0x00017500 in fpc_raiseexception ()
RT> (gdb) bt
RT> #0  0x00017500 in fpc_raiseexception ()
RT> #1  0x0010d334 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2788a20,
RT> ACALLER=0x25e9d40, ATOOL=0x2997200, this=0x27882a0)
RT> #2  0x003b7bbc in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x2997200,
RT> MACROS=0x29780c0, THEOUTPUTFILTER=0x27882a0,
RT> COMPILEROPTIONS=0x297ce90, this=0x25e9d40) at exttooldialog.pas:370
RT> #3  0x0017e458 in TBUILDMANAGER__ONRUNCOMPILERWITHOPTIONS
RT> (EXTTOOL=0x2997200, COMPOPTIONS=0x297ce90, this=0x25d8860) at buildmanager.pas:1222
RT> #4  0x0016d804 in TLAZPACKAGEGRAPH__COMPILEPACKAGE
RT> (APACKAGE=0x29ccb80, FLAGS=Invalid C/C++ type code 10 in symbol table.
RT> ) at packagesystem.pas:2947
RT> #5  0x0016ce00 in TLAZPACKAGEGRAPH__COMPILEREQUIREDPACKAGES
RT> (APACKAGE=0x0, FIRSTDEPENDENCY=0x29db0a0, GLOBALS=0x25e66d0,
RT> POLICIES=Invalid C/C++ type code 10 in symbol table.
RT> ) at packagesystem.pas:2778
RT> #6  0x0000341c in
RT> TLAZBUILDAPPLICATION__COMPILEAUTOINSTALLPACKAGES (this=0x27b8090) at lazbuild.lpr:502
RT> #7  0x000030d8 in TLAZBUILDAPPLICATION__BUILDLAZARUSIDE
RT> (this=0x27b8090) at lazbuild.lpr:445
RT> #8  0x00005c6c in TLAZBUILDAPPLICATION__RUN (this=0x27b8090) at lazbuild.lpr:978
RT> #9  0x000073b8 in PASCALMAIN () at lazbuild.lpr:1167
RT> #10 0x00029df0 in SYSTEM_FPC_SYSTEMMAIN$LONGINT$PPCHAR$PPCHAR ()
RT> #11 0x00001b6c in _start ()
RT> #12 0x00001870 in start ()
RT> (gdb) c
RT> Continuing.
RT> TOutputFilter.Execute W1
RT> TOutputFilter.Execute W2
RT> EAccessViolation : Access violation
RT>   $00148A20
RT>   $001479C4
RT>   $0014C8FC
RT>   $0014B04C
RT>   $001245B0
RT>   $0014FE68
RT>   $00150368
RT>   $0013320C
RT>   $0012B970
RT>   $00109034
RT>   $0011D3B4
RT>   $0012AADC
RT>   $0012ADF0
RT>   $0012BB78
RT> TOutputFilter.Execute W3
RT> TOutputFilter.Execute W4
RT> TOutputFilter.Execute W5
RT> TOutputFilter.Execute W6
RT> TOutputFilter.Execute W7
RT> TExternalToolList.Run Exception: there was an error
RT> ERROR: tool reported error


RT> TRoland;

RT> <<< 4.8.2008 11:56 - Roland Turcan "[hidden email]" >>>
RT>> Hello Mattias,

MG>>> /usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"

RT>> I have done all things you wrote me, but the result of compilation
RT>> didn't write any line written by WriteLn inside of IFDEFs. Maybe there
RT>> could be a bug during parsing of -d parameter and IFDEF sections were
RT>> not compiled into the code. Therefore I have commented IFDEFs out to
RT>> get them into lazbuild and the result is the following:

RT>> Compiling ./unit/ResConf.pas
RT>> Assembling resconf
RT>> An unhandled exception occurred at $00148A20 :
RT>> TOutputFilter.Execute W1
RT>> TOutputFilter.Execute W2
RT>> EAccessViolation : Access violation
RT>>   $00148A20
RT>>   $001479C4
RT>>   $0014C8FC
RT>>   $0014B04C
RT>>   $001245B0
RT>>   $0014FE68
RT>>   $00150368
RT>>   $0013320C
RT>>   $0012B970
RT>>   $00109034
RT>>   $0011D3B4
RT>>   $0012AADC
RT>>   $0012ADF0
RT>>   $0012BB78
RT>>   $00Fatal: Compilation aborted
RT>> 109034
RT>>   $0011D3B4
RT>>   $0012AADC

RT>> TOutputFilter.Execute W3
RT>> TOutputFilter.Execute W4
RT>> TOutputFilter.Execute W5
RT>> TOutputFilter.Execute W6
RT>> TOutputFilter.Execute W7
RT>> TExternalToolList.Run Exception: there was an error
RT>> ERROR: tool reported error

RT>> TRoland;


RT>> <<< 25.7.2008 0:45 - Mattias Gaertner "[hidden email]" >>>
MG>>> On Thu, 24 Jul 2008 23:58:45 +0200
MG>>> Roland Turcan <[hidden email]> wrote:

>>>> Hello Mattias,
>>>>
>>>> MG> I think the AV happens somewhere in the finally part of
>>>> MG> ide/outputfilter.pas 375.
>>>> MG> I added some verbosity in rev 15849.
>>>> MG> Please update lazarus svn and compile IDE and lazbuild clean with
>>>> MG> -dVerboseOFExecute.
>>>> MG> Then try again.
>>>>
>>>> I have tried this:
>>>>
>>>> (gdb) run
>>>> Starting program: /usr/local/share/lazarus/lazbuild
>>>> --build-ide=-dVerboseOFExecute

MG>>> Sorry. A misunderstanding.
MG>>> You need to update lazarus svn and rebuild lazbuild itself, before
MG>>> trying to use lazbuild to build your package. Which means:

MG>>> cd /usr/local/share/lazarus
MG>>> svn up
MG>>> make clean all lazbuilder
MG>>> ./lazbuild --build-ide=-va > all_output.txt

MG>>>  
>>>> and also this
>>>>
>>>> (gdb) run
>>>> Starting program: /usr/local/share/lazarus/lazbuild
>>>> --build-ide=-va-dVerboseOFExecute

MG>>> Note: Multiple parameters must be separated by space:

MG>>> /usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"

MG>>>  
>>>>[...]

MG>>> Mattias












--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Re[2]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
In reply to this post by Roland Turcan - RoTurSoft
Zitat von Roland Turcan <[hidden email]>:

> Hello Mattias,
>
> MG> /usr/local/share/lazarus/lazbuild --build-ide="-va -dVerboseOFExecute"
>
> I have done all things you wrote me, but the result of compilation
> didn't write any line written by WriteLn inside of IFDEFs. Maybe there
> could be a bug during parsing of -d parameter and IFDEF sections were
> not compiled into the code.

Or:
FPC does not automatically recompile units if a -d option is given. You must add
a -B (build all) yourself or clean up before build.
For example:

/usr/local/share/lazarus/lazbuild --build-ide="-dVerboseOFExecute -B"


> Therefore I have commented IFDEFs out to
> get them into lazbuild and the result is the following:
>
> Compiling ./unit/ResConf.pas
> Assembling resconf
> An unhandled exception occurred at $00148A20 :
> TOutputFilter.Execute W1
> TOutputFilter.Execute W2
> EAccessViolation : Access violation
>   $00148A20

ok. So, it is somewhere in EndBufferingOutput.
Can you add there some writelns and try again?

>[...]


Mattias

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Re[3]: Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

Mattias Gaertner
In reply to this post by Roland Turcan - RoTurSoft
Zitat von Roland Turcan <[hidden email]>:

> Hello Mattias,
>
> I have forgotten to send also result of building under gdb. Here is:
>
> Compiling ./unit/ResConf.pas
> Assembling resconf
> An unhandled exception occurred at $00148A20 :
>
> Breakpoint 1, 0x00017500 in fpc_raiseexception ()
> (gdb) bt
> #0  0x00017500 in fpc_raiseexception ()
> #1  0x0010d334 in TOUTPUTFILTER__EXECUTE (THEPROCESS=0x2788a20,
> ACALLER=0x25e9d40, ATOOL=0x2997200, this=0x27882a0)
> #2  0x003b7bbc in TEXTERNALTOOLLIST__RUN (EXTTOOL=0x2997200,
> MACROS=0x29780c0, THEOUTPUTFILTER=0x27882a0, COMPILEROPTIONS=0x297ce90,
> this=0x25e9d40) at exttooldialog.pas:370

Thanks. Maybe reading fProcess.ExitStatus does some strange things.
I added a check in 15949 for the WaitOnExit, so that for a terminated process
the ExitStatus is not read.

[...]

Mattias

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
12