... actually it is not always crashing at the same point:

    - Caching tokens for qx.renderer.color.ColorObject...
    - Caching tree for qx.renderer.color.ColorObject...
    - Generating tree for qx.ui.listview.ContentCellIconHtml...
    - Generating tokens for qx.ui.listview.ContentCellIconHtml...
    - Caching tokens for qx.ui.listview.ContentCellIconHtml...
    - Caching tree for qx.ui.listview.ContentCellIconHtml...
    - Generating tree for qx.renderer.layout.CanvasLayoutImpl...
    - Generating tokens for qx.renderer.layout.CanvasLayoutImpl...
    - Caching tokens for qx.renderer.layout.CanvasLayoutImpl...
make: *** [exec-script-source] Terminated

so it must be a memory issue or something. How can I monitor this? Any 
system logfile that would spit out warning messages?

C.

Christian Boulanger schrieb:
> Hello Derrell,
>
> I tried "VERBOSE = true" and replacing the first line of generator.py by
> #!/usr/bin/python2.3
> same thing: "make: *** [exec-script-source] Terminated"
>
> then I figured out that the error occurred in the make target 
> "exec-script-source". By looking around in unfamiliar territory of 
> python and make-files, I found imp.mk where the exec-script-source 
> target was defined, and I added a --verbose option there.
>
> make distclean
> make source
>
> and the verbose output flowed.... until this point:
>
>     - Generating tree for qx.ui.core.Widget...
>     - Generating tokens for qx.ui.core.Widget...
>     - Caching tokens for qx.ui.core.Widget...
>     - Caching tree for qx.ui.core.Widget...
>     - Following user hint, adding #use(qx.component.init.Gui) into class 
> qx.ui.core.Widget
>     - Removing runtime qx.Class which is already defined in loadtime table.
>     - Removing runtime qx.core.Variant which is already defined in 
> loadtime table.
>     - Removing runtime qx.core.Setting which is already defined in 
> loadtime table.
>     - Generating tree for qx.ui.listview.HeaderCell...
>     - Generating tokens for qx.ui.listview.HeaderCell...
> make: *** [exec-script-source] Terminated
>
> maybe it is a memory issue? argh, I want this to work!
>
> C.
>
>
>
>
>
> [EMAIL PROTECTED] schrieb:
>
>   
>> Christian Boulanger <[EMAIL PROTECTED]> writes:
>>
>>   
>>     
>>> Derrel:
>>>
>>> thank you for this, this is the spirit of the open source community!!
>>>
>>> I use a Debian Sarge with repositories testing and unstable added, maybe 
>>> this
>>> might create a problem?
>>>
>>> I attach the output of the commands. Unfortunately, same result as before. 
>>> Is
>>> there a debug log or debug mode of the make process?
>>>
>>> Thank you, and it would be great if you can find out something.
>>>     
>>>       
>> Your versions of python and make are newer than mine.  I'm using
>> Lindows... er... Linspire, which is derived from Debian Sarge.  Since this is
>> dying in a python script, I suppose it's possible that the newer version of
>> python has some bug.
>>
>> There is a verbose mode at the makefile level: you can add "VERBOSE = true" 
>> to
>> your makefile.  That will show you the commands that it's executing.  It's
>> dying in frontend/framework/tool/generator.py.  I'm not at all familiar with
>> the inner workings of that tool.  There may be a debug or verbose option in
>> it, too, and once you turn on the verbose option in the makefile, you'll have
>> the command it's executing that you could modify to enable verbose or debug 
>> in
>> generator.py if it's available.
>>
>> The next thing I'd do, I think, is run generator.py exactly as the makefile 
>> is
>> doing it, but run it under 'strace' to see exactly why it's dying.  Other 
>> than
>> that, maybe you could try your hand at adding some debug statements in
>> generator.py...
>>
>> Sorry I haven't solved the problem, but hopefully I've at least given you a
>> direction to move forward... :-(
>>
>> Please let me know what ends up being the problem.
>>
>> Derrell
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>   
>>     
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to