Dan,
I have managed to capture another segfault in MEM2 release 0.5.2.

Here is a gdb session.  Let me know what else I can do to help track
this down.

marc:[skit]$ gdb ruby
GNU gdb 6.6.90.20070912-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run ./skit --diff tests/REGRESS_SRC tests/REGRESS_SRC2 --generate
Starting program: /usr/bin/ruby ./skit --diff tests/REGRESS_SRC
tests/REGRESS_SRC2 --generate
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7cde8c0 (LWP 3549)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7cde8c0 (LWP 3549)]
0xb7c50ea2 in ruby_xml_xpath_object_first (self=3080810320)
    at ruby_xml_xpath_object.c:165
165       switch(xpop->nodesetval->nodeTab[0]->type) {
(gdb) bt
#0  0xb7c50ea2 in ruby_xml_xpath_object_first (self=3080810320)
    at ruby_xml_xpath_object.c:165
#1  0xb7ebd145 in ?? () from /usr/lib/libruby1.8.so.1.8
#2  0xb7a16f50 in ?? ()
#3  0xbfa6ef20 in ?? ()
#4  0xb7a17b94 in ?? ()
#5  0xb7ebd13a in ?? () from /usr/lib/libruby1.8.so.1.8
#6  0xb7ca85fc in ?? ()
#7  0xb7a1842c in ?? ()
#8  0xb7a18454 in ?? ()
#9  0xb7cdb7e0 in ?? ()
#10 0x00000000 in ?? ()
(gdb) 

__
Marc

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
libxml-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/libxml-devel

Reply via email to