[xsd-users] tree/default/general test failed

Antonio Trande anto.trande at gmail.com
Sun Oct 11 12:30:46 EDT 2015


Sorry, xerces-c debuginfo was not installed correctly; this is the new log
on CentOS-6:

> (gdb) run cxx-tree --generate-inline --generate-ostream
--generate-serialization --generate-default-ctor --generate-from-base-ctor
--std c++98 --output-dir home/Anto.Trande/Downloads
/home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd
Starting program: /usr/bin/xsdcxx cxx-tree --generate-inline
--generate-ostream --generate-serialization --generate-default-ctor
--generate-from-base-ctor --std c++98 --output-dir
home/Anto.Trande/Downloads
/home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd
[Thread debugging using libthread_db enabled]
warning: "/usr/lib/debug/usr/lib64/libicudata.so.42.1.debug": separate
debug info file has no debug info

Program received signal SIGSEGV, Segmentation fault.
getId (this=0x0, prefixToMap=0xadf7f0, mode=<value optimized out>,
unknown=@0x7fffffffb21f) at xercesc/util/StringPool.hpp:141
141        PoolElem* elemToFind = fHashTable->get(toFind);
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y

Starting program: /usr/bin/xsdcxx cxx-tree --generate-inline
--generate-ostream --generate-serialization --generate-default-ctor
--generate-from-base-ctor --std c++98 --output-dir
home/Anto.Trande/Downloads
/home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd
[Thread debugging using libthread_db enabled]
warning: "/usr/lib/debug/usr/lib64/libicudata.so.42.1.debug": separate
debug info file has no debug info

Program received signal SIGSEGV, Segmentation fault.
getId (this=0x0, prefixToMap=0xadf7f0, mode=<value optimized out>,
unknown=@0x7fffffffb21f) at xercesc/util/StringPool.hpp:141
141        PoolElem* elemToFind = fHashTable->get(toFind);


On Sun, Oct 11, 2015 at 4:53 PM, Antonio Trande <anto.trande at gmail.com>
wrote:

> I tried to debug this error (note that XSD has been patched and renamed to
> 'xsdcxx' because of conflicts with other 'xsd' executables):
>
> > gdb xsdcxx
> > (gdb) run cxx-tree --generate-inline --generate-ostream
> --generate-serialization --generate-default-ctor --generate-from-base-ctor
> --std c++98 --output-dir home/Anto.Trande/Downloads
> /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd
> Starting program: /usr/bin/xsdcxx cxx-tree --generate-inline
> --generate-ostream --generate-serialization --generate-default-ctor
> --generate-from-base-ctor --std c++98 --output-dir
> home/Anto.Trande/Downloads
> /home/Anto.Trande/Downloads/xsd-4.0.0-7.el6.src/xsd-4.0.0+dep/xsd/tests/cxx/tree/default/general/test.xsd
> warning: the debug information found in
> "/usr/lib/debug//usr/lib64/libxerces-c-3.0.so.debug" does not match
> "/usr/lib64/libxerces-c-3.0.so" (CRC mismatch).
>
> warning: the debug information found in
> "/usr/lib/debug/usr/lib64/libxerces-c-3.0.so.debug" does not match
> "/usr/lib64/libxerces-c-3.0.so" (CRC mismatch).
>
> [Thread debugging using libthread_db enabled]
> warning: "/usr/lib/debug/usr/lib64/libicudata.so.42.1.debug": separate
> debug info file has no debug info
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff79c54b5 in xercesc_3_0::ElemStack::mapPrefixToURI(unsigned
> short const*, xercesc_3_0::ElemStack::MapModes, bool&) const ()
>    from /usr/lib64/libxerces-c-3.0.so
>
> Note:
> xerces-c version 3.0.1 (CentOS-6): test failed
> xerces-c version 3.1.1 (Fedora and CentOS-7): test works
>
>
>
> On Sat, Oct 10, 2015 at 12:12 PM, Antonio Trande <anto.trande at gmail.com>
> wrote:
>
>> On 10/10/2015 11:42 AM, Boris Kolpackov wrote:
>> > Hi Antonio,
>> >
>> > Antonio Trande <anto.trande at gmail.com> writes:
>> >
>> > > Please, does anyone know why happens?
>> >
>> > Any chance of getting the stack trace from the core?
>> Unfortunately, i can't in this moment.
>>
>> >Also, knowing a bit more about the environment would help, especially,
>> the GCC version that is being used.
>>
>> XSD is rebuilt locally in a CentOS6 chroot build-system (on a Fedora 22)
>> with GCC-4.4.7 (as you can see from log).
>>
>> The tests do not fail in Fedora with GCC-5.1.1 [1] and in a CentOS7
>> chroot with GCC-4.8.3 [2].
>>
>> [1]https://kojipkgs.fedoraproject.org//work/tasks/7081/11397081/build.log
>> [2]https://kojipkgs.fedoraproject.org//work/tasks/7187/11397187/build.log
>> >
>> > Boris
>> >
>>
>> --
>> Antonio Trande
>>
>> mailto: sagitter 'at' fedoraproject 'dot' org
>> http://fedoraos.wordpress.com/
>> https://fedoraproject.org/wiki/User:Sagitter
>> GPG Key: 0x565E653C
>> Check on https://keys.fedoraproject.org/
>>
>
>
>
> --
>
> *Antonio Trande"Fedora Ambassador"*
> *"Fedora italian translation group"*
>
>
> *"Blogger"**mail*: mailto:sagitter at fedoraproject.org
> <sagitter at fedoraproject.org>
> *Homepage*: http://www.fedora-os.org
> *Sip Address* : sip:sagitter AT ekiga.net
> *Jabber <http://jabber.org/>* :sagitter AT jabber.org
> *GPG Key: **D400D6C4*
>



-- 

*Antonio Trande"Fedora Ambassador"*
*"Fedora italian translation group"*


*"Blogger"**mail*: mailto:sagitter at fedoraproject.org
<sagitter at fedoraproject.org>
*Homepage*: http://www.fedora-os.org
*Sip Address* : sip:sagitter AT ekiga.net
*Jabber <http://jabber.org/>* :sagitter AT jabber.org
*GPG Key: **D400D6C4*


More information about the xsd-users mailing list