[4suite-dev] Re: [4suite] Last call for heavy testing

[Jeremy Kloth]

On Monday, September 25, 2006 12:22 am, Ross Jekel wrote:
> Jeremy Kloth writes:
> >> > For Python2.5 compiled on SuSE 9.2 AMD64, I'm still getting the
> >> > segmentation fault:
> >> >
> >> > Let me know what I can do to help find the segfault on my machine if
> >> > you can't repro it. I did not try to run under 2.5 with this build.
> >
> > Um, did you test with 2.5 or not? These two statements are contradicting.
> > Either way, a gdb backtrace would be quite useful.
>
> Sorry for the misunderstanding. The segfault happened during the build_docs
> phase of setup, so what I meant was that I did not test running 4Suite in
> my application.
>
> I tried the CVS branch. Here's how I got it.
>
> cvs -d:pserver:anonymous at cvs.4suite.org:/var/local/cvsroot checkout -r
> XML1_0-maint 4Suite
>
> Compiling with 2.4.3 AMD 64 bit, I now only get this compiler warning and
> an install warning:
>
> Ft/Rdf/Parsers/Versa/VersaParser.c: In function `lexer_match':
> Ft/Rdf/Parsers/Versa/VersaParser.c:1800: warning: int format, different
> type arg (arg 2)
> warning: install_localstate: no files found matching
> 'Ft/Server/Share/Data/README'

This is now fixed in current CVS.

> Compiling with 2.5 AMD 64 bit, I get the same warning as above.
>
> Also, I still get the Segfault. Here's a gdb session (let me know if you
> need more):
>
> jekel at linux:~/4Suite> sudo gdb python2.5
> Password:
> GNU gdb 6.2.1
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "x86_64-suse-linux"...Using host libthread_db
> library "/lib64/tls/libthread_db.so.1".
>
> (gdb) run setup.py install
> Starting program: /usr/local/bin/python2.5 setup.py install
> [Thread debugging using libthread_db enabled]
> [New Thread 182902069504 (LWP 13715)]
> running install
> running build
> running config
> running build_py
> running build_ext
> running build_scripts
> running build_docs
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 182902069504 (LWP 13715)]
> _PyUnicode_New (length=-5317147200092896306) at unicodeobject.c:280
> 280         unicode->str[length] = 0;
> (gdb) bt
> #0  _PyUnicode_New (length=-5317147200092896306)
>    at unicodeobject.c:280
> #1  0x0000000000479537 in PyUnicodeUCS2_DecodeUTF8Stateful (s=Variable "s"
> is not available.
> )
>    at unicodeobject.c:1228
> #2  0x000000000047bad0 in PyUnicodeUCS2_Decode (s=Variable "s" is not
> available.
> )
>    at unicodeobject.c:1206
> #3  0x0000002a981c3f92 in string_isxml (self=Variable "self" is not
> available.
> ) at xmlstring.c:525

That pointed me to the problem immediately, thank you.  This is also now fixed 
in CVS.

Would it be possible for you to try again after updating to the lastest CVS?  
This is really helping us greatly.

-- 
Jeremy Kloth
http://4suite.org/