At 14.46 22/11/2004 -0500, White Daniel E CONT DLVA wrote:
Do you have Qt as well ? I found the QDom classes easier to use in
extracting info and constructing documents.
No, but it looks like I can download them.
Alberto
-
To uns
ubject: RE: Segmentation Fault on a reused XercesDOMParser -- HELP
PLEASE !!
At 11.28 22/11/2004 -0500, White Daniel E CONT DLVA wrote:
>Yes, I can try.
>
>Would it complicate matters that I am using ACE ?
No, I have it on my machine.
Alberto
>-Original Message-
>From: Alber
PROTECTED]
Subject: RE: Segmentation Fault on a reused XercesDOMParser -- HELP
PLEASE !!
Importance: High
Hi Daniel,
can you package a small test case that reproduces the error?
Thanks,
Alberto
At 11.07 22/11/2004 -0500, White Daniel E CONT DLVA wrote:
>It still spews. I even tried adding a call
Yes, I can try.
Would it complicate matters that I am using ACE ?
-Original Message-
From: Alberto Massari [mailto:[EMAIL PROTECTED]
Sent: Monday, November 22, 2004 11:18 AM
To: [EMAIL PROTECTED]
Subject: RE: Segmentation Fault on a reused XercesDOMParser -- HELP
PLEASE !!
Importance
know.
-Original Message-
From: White Daniel E CONT DLVA [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 10:52 AM
To: '[EMAIL PROTECTED]'; 'Alberto Massari'
Subject: RE: Segmentation Fault -- HELP PLEASE !!
Could my problem be in wanting to re-use the parser object
EMAIL PROTECTED]'; 'Alberto Massari'
Subject: RE: Segmentation Fault -- HELP PLEASE !!
Could my problem be in wanting to re-use the parser object ?
How do other folks do this ?
Would I be better off creating a fresh parser for each incoming statement
and then deleting it when I have
PROTECTED]
Sent: Friday, November 19, 2004 9:06 AM
To: '[EMAIL PROTECTED]'; 'Alberto Massari'
Subject: RE: Segmentation Fault -- HELP PLEASE !!
As a matter of fact, yes, but each thread has its own instance of the
parser. It is created after the thread is activated.
I found som
about anything else that might need cleaning up ?
-Original Message-
From: Alberto Massari [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 6:00 PM
To: [EMAIL PROTECTED]
Subject: RE: Segmentation Fault -- HELP PLEASE !!
Importance: High
Hi Daniel,
by any chance, is the method
Hi Daniel,
by any chance, is the method myStreamHandler::validate run by multiple threads?
Alberto
At 11.45 18/11/2004 -0500, White Daniel E CONT DLVA wrote:
I have reached wits end on this one.
I am running on RedHat 7.1, with gcc's 2.96-112.7.1
I even applied the fix-patch from XERCESC-1162 about
170]
xercesc_2_6::RefHash2KeysTableOf::removeAll(void)
[RefHash2KeysTableOf.c:207]
xercesc_2_6::RefHash2KeysTableOf::~RefHash2KeysTabl
eOf(void) [RefHash2KeysTableOf.c:152]
xercesc_2_6::TraverseSchema::cleanUp(void) [TraverseSchema.cpp:8415]
* Received signal 11 (SIGSEGV - Segmentation fa
Hi,
I am confronting a problem with xerces-c 2.4.0. Code below runs properly on Linux/Windows but
on freebsd box it throws a segmentation fault. I have gcc version
(3.2.3)
#include #include
#include
#include
#include
#include
#include
#include
#include
#include
#include
LL pointer and try to run XTOC on it, and you will get the
segmentation fault.
A more robust code would be
{
if(XMLString::equals(name,g_theElementIamLookingFor))
{
const XMLCh* value=attributes.getValue("Value");
if(value)
Hi,
I write the part of SAX code:
void MyProject::startElement(const XMLCh* constname
, AttributeList& attributes)
{
int r;
int pippo=atoi(XTOC(attributes.getValue("Value")));
cout << pippo;
The output code is:
Segmentation fa
:[EMAIL PROTECTED]]
Sent: 04 December 2003 18:48
To: [EMAIL PROTECTED]
Subject: Re: segmentation fault while writing apache modules using
xerces
Hi!
I guess the problem is not on the apachemodule.
I've just made a program with parts of module code that uses xercestool
Hi
There,
Just a really stupid question are you using the
XMLPlatformUtils::Initialize(); method
Thanks
Pete
-Original Message-From:
Hugo Kotsubo [mailto:[EMAIL PROTECTED]Sent: 04 December 2003
18:48To: [EMAIL PROTECTED]Subject: Re:
segmentation fault while writing
To: [EMAIL PROTECTED]
.com.br> cc: (bcc: David N Bertoni/Cambridge/IBM)
Subject: Re: segmen
TED]
.com.br> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Re: segmentation fault while
writing apache modules using
Title: Message
Did
you call XMLPlatformUtils::Initialize() before creating the
parser?
-Original Message-From: Hugo Kotsubo
[mailto:[EMAIL PROTECTED] Sent: Thursday, December 04, 2003
1:48 PMTo: [EMAIL PROTECTED]Subject: Re:
segmentation fault while writing apache
Hi!
I guess the problem is not on the apache module.
I've just made a program with parts of module code that uses xerces tools
and
the program also crashes..
I've got a segfault when I try to create a parser with new operator:
XercesDOMParser *parser = new XercesDOMParser;
Why my program
Hi!
Scott, thanks for your help.
Well, all modules in my httpd server are using the same version of libstdc++
So, I still don't know what is happening..
Any clues?
tks
Hugo
Scott Cantor wrote:
I'm compiling the module with g++ and installing with 'apxs -i'
I would skip
> I'm compiling the module with g++ and installing with 'apxs -i'
I would skip the apxs stuff until you have it working. But as long as you're
linking with g++, my guess is the crash is from two versions of libstdc++
getting loaded into Apache by different modules.
-- Scott
I'm compiling the module with g++ and installing with 'apxs -i'
Here's the Makefile:
##
# the used tools
APXS=apxs
APACHECTL=apachectl
# Get all of apxs's internal values.
APXS_CC=`$(APXS) -q CC`
APXS_TARGET=`$(APXS) -q TARGE
How are you linking your module, and are there any other modules being
loaded that use C++ that are built with an older libstdc++? The latter will
cause the behavior you're seeing.
mod_php is a common culprit, since it uses C++.
-- Scott
-
Hi
I'm writting an apache module that uses xerces for process form data and
build xml files with this data.
I wrote the module in C++, compiled, installed with apxs, restarted the
httpd server and everything is fine.
But when the module runs, I've got a segmentation fault. After de
gzilla/show_bug.cgi?id=7307
DOM Parser's ErrorHandler Class's fatalError() function generates Segmentation Fault
[EMAIL PROTECTED] changed:
What|Removed |Added
gzilla/show_bug.cgi?id=3771
Segmentation Fault on RedHat 7.1
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Additional Comment
gzilla/show_bug.cgi?id=3771
Segmentation Fault on RedHat 7.1
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=9460
DOMParser segmentation fault when reading from MemBufInputSource
--- Additional Comments From [EMAIL PROTECTED] 2002-05-31 12:46 ---
The problem comes from the fact that SUSE and RedHat use different compilers
with incompatible C++ ABIs. E.g. it's a clash
gzilla/show_bug.cgi?id=9460
DOMParser segmentation fault when reading from MemBufInputSource
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=9460
DOMParser segmentation fault when reading from MemBufInputSource
--- Additional Comments From [EMAIL PROTECTED] 2002-05-31 10:59 ---
I seem to have a compile/link problem - I am using SUSE Linux 7.1:
The binary samples of version 1.7 work on my PC, but when I c
gzilla/show_bug.cgi?id=9460
DOMParser segmentation fault when reading from MemBufInputSource
Summary: DOMParser segmentation fault when reading from
MemBufInputSource
Product: Xerces-C++
Version: 1.7.0
Platform: PC
OS/Version:
gzilla/show_bug.cgi?id=7307
DOM Parser's ErrorHandler Class's fatalError() function generates Segmentation Fault
[EMAIL PROTECTED] changed:
What|Removed |Added
All,
I get the following segmentation fault
Segmentation fault in parse__9DOMParserFRC11InputSourceCb at
0xd31c261c ($t1)
0xd31c261c (parse__9DOMParserFRC11InputSourceCb+0x84) 981e002c
stb r0,0x2c(r30)
when I call
parser->parse(input);
parser is: SAXPar
gzilla/show_bug.cgi?id=7307
DOM Parser's ErrorHandler Class's fatalError() function generates Segmentation Fault
[EMAIL PROTECTED] changed:
What|Removed |Added
nking
and that's all), it cause segmentation fault when doing the
parser->parse(...) .
I do gdb and backtrace, it shows:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 9684)]
0x08080335 in Ptr >::~Ptr () at
ConfigParser.cc:114
114 }
(gdb) backtr
gzilla/show_bug.cgi?id=7307
DOM Parser's ErrorHandler Class's fatalError() function generates Segmentation Fault
--- Additional Comments From [EMAIL PROTECTED] 2002-03-27 18:01 ---
I tried building the parser on Solaris 8 with Forte 6 U 1, with Lowest
OPTIMIZATION LEVEL = 1 (ins
gzilla/show_bug.cgi?id=7307
DOM Parser's ErrorHandler Class's fatalError() function generates Segmentation Fault
--- Additional Comments From [EMAIL PROTECTED] 2002-03-25 16:24 ---
I also see the same problem, if the XML file does not exist. This happens
whether or not I set a h
gzilla/show_bug.cgi?id=7307
DOM Parser's ErrorHandler Class's fatalError() function generates Segmentation Fault
Summary: DOM Parser's ErrorHandler Class's fatalError() function
generates Segmentation Fault
Product: Xerces-C++
gzilla/show_bug.cgi?id=4924
Core Dump ( Segmentation fault ) during the instance creation of XSLTInputSource
with const char* passed to constructor
[EMAIL PROTECTED] changed:
What|Removed
gzilla/show_bug.cgi?id=5457
Segmentation fault if schema file not found
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=5457
Segmentation fault if schema file not found
Summary: Segmentation fault if schema file not found
Product: Xerces-C++
Version: 1.5.2
Platform: Other
OS/Version: Linux
Status: NEW
Severity:
gzilla/show_bug.cgi?id=4924
Core Dump ( Segmentation fault ) during the instance creation of XSLTInputSource
with const char* passed to constructor
--- Additional Comments From [EMAIL PROTECTED] 2001-11-16 07:37 ---
Does your code call XMLPlatformUtils::Initialize()?
That is
gzilla/show_bug.cgi?id=4924
Core Dump ( Segmentation fault ) during the instance creation of XSLTInputSource
with const char* passed to constructor
Summary: Core Dump ( Segmentation fault ) during the instance
creation of XSLTInputSource with const char*
gzilla/show_bug.cgi?id=3771
Segmentation Fault on RedHat 7.1
[EMAIL PROTECTED] changed:
What|Removed |Added
Priority|Other
gzilla/show_bug.cgi?id=3771
Segmentation Fault on RedHat 7.1
--- Additional Comments From [EMAIL PROTECTED] 2001-09-21 13:09 ---
Created an attachment (id=595)
This is the gdb trace "gdb a.out core; bt"
-
To uns
gzilla/show_bug.cgi?id=3771
Segmentation Fault on RedHat 7.1
--- Additional Comments From [EMAIL PROTECTED] 2001-09-21 13:08 ---
Created an attachment (id=594)
Base program
-
To unsubscribe, e-mail: [EMAIL PROTECTE
gzilla/show_bug.cgi?id=3771
Segmentation Fault on RedHat 7.1
--- Additional Comments From [EMAIL PROTECTED] 2001-09-21 13:08 ---
Created an attachment (id=593)
Makefile used
-
To unsubscribe, e-mail: [EMAIL PROTECTE
gzilla/show_bug.cgi?id=3771
Segmentation Fault on RedHat 7.1
Summary: Segmentation Fault on RedHat 7.1
Product: Xerces-C++
Version: 1.5.1
Platform: Other
OS/Version: Linux
Status: NEW
Severity: Blocker
Priority:
We are using Xerces-C1_4 on a two-processor Sun box running Solaris 8. There
appears to be no problem in a single-threaded app, however, a multi-threaded
app fails. I have created a test code that makes simple Xerces calls and
which fails in a multi-threaded environment. The test code can be run
i
-2.10.0.so), so
we add the comented option to the Makefile and we solve the problem... (!).
Well, thanks all
Harald.
- Mensaje original -
De: "Stefan Brauneis" <[EMAIL PROTECTED]>
Para: <[EMAIL PROTECTED]>
Enviado: martes 8 de mayo de 2001 13:09
Asunto: Re: xerces 1.4
or example
> DOMCount), I receive "segmentation fault" error.
> I suspect about the std c++ library because is there where the segmentation
> fault occurs in createReader member of ReaderMgr class.
> Which version are you using?
> Is this the correct version?
> Someone is u
Hi all.
My version of the std c++ library is "libstdc++-2.96-69" (in Redhat linux: rpm
-qa | grep std). The examples distributed with the xerces library runs without
problems, but when I compile the source code of any example (for example
DOMCount), I receive "segmentation
[EMAIL PROTECTED]
<[EMAIL PROTECTED]cc: (bcc: David N Bertoni/CAM/Lotus)
m.com> Subject: Unsupported encoding cause
t the encoding is unsupported.
When I use Xalan, I am getting a segmentation fault. The fault occurs in
the vector operator bool routine. This is called by StylesheetHandler.cpp,
line 1708. Looking at the code, it is not clear why a segmentation fault
would occur, because StylesheetHandler has an a
54 matches
Mail list logo
