workbench >= r757 crashes on IRIX.

Hi Barry,

I installed Workbench r782 on an IRIX machine today.
It crashes the python interpreter with a segmentation fault.

Unfortunately, the dbx IRIX debugger is getting into a loop
showing the same stack entry over and over:

Thread 0x10000
>  0 strlen(0x0, 0x60d0e48, 0x0, 0xfe, 0x32, 0x2, 0x7f,
0x27)
["/xlv44/6.5.28m/work/irix/lib/libc/libc_n32_M4/strings
/strlen.s":58, 0xfa42fb0]
   1 PyString_FromString(str = (nil))
["/opt/local/source/Python-2.4.2/Objects/stringobject.c
":101, 0x10066894]
   2 PyString_FromString(str = (nil))
["/opt/local/source/Python-2.4.2/Objects/stringobject.c
":101, 0x10066894]
   3 PyString_FromString(str = (nil))
["/opt/local/source/Python-2.4.2/Objects/stringobject.c
":101, 0x10066894]
   4 PyString_FromString(str = (nil))
["/opt/local/source/Python-2.4.2/Objects/stringobject.c
":101, 0x10066894]

So that did not help much.

I knew that older versions of Workbench did not crash,
so I installed one after another and found out that r757
is the first one that crashes.

The same workbench does not crash on Linux, which is
a bit odd.

Is the above information sufficient for you to fix the bug?

Carsten.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribepysvn.tigris.org
For additional commands, e-mail: dev-helppysvn.tigris.org

Carsten Koch wrote:
...
> Unfortunately, the dbx IRIX debugger is getting into a
loop

I also built and tried gdb 6.5, but that did not work
either.
I used "python -v" to find out what got loaded
last.

import xml # directory /opt/local/lib/python2.4/xml
# /opt/local/lib/python2.4/xml/__init__.pyc matches
/opt/local/lib/python2.4/xml/__init__.py
import xml # precompiled from
/opt/local/lib/python2.4/xml/__init__.pyc
import xml.parsers # directory
/opt/local/lib/python2.4/xml/parsers
# /opt/local/lib/python2.4/xml/parsers/__init__.pyc matches
/opt/local/lib/python2.4/xml/parsers/__init__.py
import xml.parsers # precompiled from
/opt/local/lib/python2.4/xml/parsers/__init__.pyc
# /opt/local/lib/python2.4/xml/parsers/expat.pyc matches
/opt/local/lib/python2.4/xml/parsers/expat.py
import xml.parsers.expat # precompiled from
/opt/local/lib/python2.4/xml/parsers/expat.pyc
dlopen("/opt/local/lib/python2.4/lib-dynload/pyexpat.so
", 2);
Segmentation fault (core dumped)

So this may be a problem with pyexpat.so.

Is there a way to run workbench without xml?

Carsten.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribepysvn.tigris.org
For additional commands, e-mail: dev-helppysvn.tigris.org

On Dec 15, 2006, at 23:16, Carsten Koch wrote:

> Carsten Koch wrote:
> ...
>> Unfortunately, the dbx IRIX debugger is getting
into a loop
>
> I also built and tried gdb 6.5, but that did not work
either.
> I used "python -v" to find out what got
loaded last.
>
> import xml # directory /opt/local/lib/python2.4/xml
> # /opt/local/lib/python2.4/xml/__init__.pyc matches
/opt/local/lib/ 
> python2.4/xml/__init__.py
> import xml # precompiled from
/opt/local/lib/python2.4/xml/ 
> __init__.pyc
> import xml.parsers # directory
/opt/local/lib/python2.4/xml/parsers
> # /opt/local/lib/python2.4/xml/parsers/__init__.pyc
matches /opt/ 
> local/lib/python2.4/xml/parsers/__init__.py
> import xml.parsers # precompiled from
/opt/local/lib/python2.4/xml/ 
> parsers/__init__.pyc
> # /opt/local/lib/python2.4/xml/parsers/expat.pyc
matches /opt/local/ 
> lib/python2.4/xml/parsers/expat.py
> import xml.parsers.expat # precompiled from
/opt/local/lib/ 
> python2.4/xml/parsers/expat.pyc
>
dlopen("/opt/local/lib/python2.4/lib-dynload/pyexpat.so
", 2);
> Segmentation fault (core dumped)
>
> So this may be a problem with pyexpat.so.

This makes sense as r757 was the first to switch to XML for
the ini  
file.

> Is there a way to run workbench without xml?

I need XML for the ini file.

You need to get pyexpat fixed.

You can run the wb_preferences.py code in test mode.
Put a copy of your WorkBench.xml in /tmp/t,xml.

If its pyexpat.so only then you should get the bus error.

Barry



------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribepysvn.tigris.org
For additional commands, e-mail: dev-helppysvn.tigris.org

Barry Scott wrote:
...
> You need to get pyexpat fixed.

I built gcc 4.1.1 on IRIX and re-built the tool chain with
it.
That took about a week since I have a slow IRIX machine at
home.

I also noticed that I had expat 2.0.0 installed with the old
tool
chain, while Python, subversion and wx use 1.95.x, so I used
1.95.8
for the new tool chain.
I also re-installed the 1.95.8 expat after the subversion
build
overwrote it with its own version.
I also fixed the 1.95.8 build so it installs both needed
header files,
which apparently did not work on IRIX.

I do not know which one of the above fixed it, but now
workbench >= r757 is working on IRIX.


Carsten.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribepysvn.tigris.org
For additional commands, e-mail: dev-helppysvn.tigris.org