Could i suggest a further test?
try SEnumval or SAXPrint or DOMPrint and see what you get. i am betting that you wont get any output that comes from the actual elements....those where the ones that i was trying. if it coredumps, and dumps in the same place, that would be enlightening. if it dies elsewhere, that would be enlightening too... i am currently *guessing* after looking at your backtrace that the XML chars are sized incorrectly in some portion of the code, but not all of it. thus, too big things are getting stuffed into too small holes and then bad things are happening/ On Thu, 28 Feb 2002, Christian Kruse wrote: > Hoi, > > On Thu, 28 Feb 2002 11:26:49 -0800 (PST) > John Utz <[EMAIL PROTECTED]> wrote: > > > well, if you got it to actually parse, u are ahead of me! > > > > On Thu, 28 Feb 2002, Christian Kruse wrote: > > > >> [...] > > the warnings are not a problem, imho. they are a 'security warning'. > > I thougt so, too :-) > > > > The binary works fine, but it core dumps after the 'return 0' at the end of > > > the samples. Can anybody help me with it? I don't know why it core dumps... > > > > well, as i said above, when i built xerces on my 4.4 box, it ran the > > samples, but never seemd to parse the document. > > It parses the document. It's output is correct. I think a destructor of an > object causes this core dump. > > > i would suggest checking that you built a debug version ( was compiled > > with -g ) and then if it's a debug version, checking the core dump with > > gdb. > > Done. > > > i think the command line would be: > > > > gdb xercesapp xercesapp.core > > > > then when it finishes loading, type: > > > > bt > > > > and then look at the results, it will say which line in which function > > caused the core dump > > bash-2.05a$ gdb SAXCount SAXCount.core > GNU gdb 4.18 > Copyright 1998 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 "i386-unknown-freebsd"... > Core was generated by `SAXCount'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/local/xerces-c-src1_6_0/lib/libxerces-c1_6_0.so... > done. > Reading symbols from /usr/lib/libstdc++.so.3...done. > Reading symbols from /usr/lib/libm.so.2...done. > Reading symbols from /usr/lib/libc.so.4...done. > Reading symbols from /usr/lib/libc_r.so.4...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > #0 0x283db3b6 in xdr_u_int () from /usr/lib/libc.so.4 > (gdb) run test.xml > Starting program: /usr/local/xerces-c-src1_6_0/samples/SAXCount/SAXCount test.xml > test.xml: 4 ms (4 elems, 0 attrs, 10 spaces, 0 chars) > > Program received signal SIGSEGV, Segmentation fault. > 0x283db3b6 in xdr_u_int () from /usr/lib/libc.so.4 > (gdb) bt > #0 0x283db3b6 in xdr_u_int () from /usr/lib/libc.so.4 > #1 0x283dbb1a in xdr_bytes () from /usr/lib/libc.so.4 > #2 0x283dbbec in xdr_netobj () from /usr/lib/libc.so.4 > #3 0x283f1416 in .cerror () from /usr/lib/libc.so.4 > #4 0x283f1317 in exit () from /usr/lib/libc.so.4 > #5 0x804912f in _start () > (gdb) > > Any ideas? > > Greets, > CK > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
