Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 43720 invoked from network); 6 Oct 2008 13:42:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Oct 2008 13:42:00 -0000 Received: (qmail 12793 invoked by uid 500); 6 Oct 2008 13:41:58 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 12773 invoked by uid 500); 6 Oct 2008 13:41:58 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 12762 invoked by uid 99); 6 Oct 2008 13:41:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Oct 2008 06:41:58 -0700 X-ASF-Spam-Status: No, hits=2.1 required=10.0 tests=DNS_FROM_SECURITYSAGE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of supun06@gmail.com designates 209.85.200.171 as permitted sender) Received: from [209.85.200.171] (HELO wf-out-1314.google.com) (209.85.200.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Oct 2008 13:40:55 +0000 Received: by wf-out-1314.google.com with SMTP id 25so2747448wfc.28 for ; Mon, 06 Oct 2008 06:41:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=0wDy9m2INWZZyqs/lGYCKPpupTtmtf6D0cBMZvHJmYM=; b=Kf5GEP7hx57eHrfPRU960weh4IrM99cvuiq0lF2+hJ3P7tmvtJLgEdGSB7IHIv/d+l 9E6nbXASNrli3loBR3932YFOhZtyYZdDK25ZgUIYF5xyMxWceq7AH/c8nQJvjLcRrSre wdCcWGwDh3zdvyLTXQ7YQvdGOr1o+Kjlj8Fvw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=NO0qoQG0vHadkd8CwbqPrqzBUSVe3Q3UUvHdJzOoe15d3+nR7vIYc+8AZ529m5AVX7 ya+G3Xr/l/SxZ7gU32cYyu0VvZ9RMoAx4kKX7270/Ayx2vwpKq8Hh+NwUqHr/yP2ffYk TZm2CSSOFfaKKC9DpCkUMXLT29rx42MCwsgus= Received: by 10.114.135.1 with SMTP id i1mr5531206wad.5.1223300481313; Mon, 06 Oct 2008 06:41:21 -0700 (PDT) Received: by 10.114.124.15 with HTTP; Mon, 6 Oct 2008 06:41:21 -0700 (PDT) Message-ID: Date: Mon, 6 Oct 2008 18:41:21 +0500 From: "Supun Kamburugamuva" To: "Apache AXIS C Developers List" Subject: Re: Axis2/c debug mode problem In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24960_26250688.1223300481312" References: X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_24960_26250688.1223300481312 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline When you use libxml2 you need to define the AXIS2_LIBXML2_ENABLED pre-processor directive in the axiom project. I think this is the cause of this error. I realized this only when I go though the code. Supun. On Mon, Oct 6, 2008 at 6:31 PM, Supun Kamburugamuva wrot= e: > The chances are very small to a bug like this to be in libxml2 as it is a > very well tested and widely used XML library. If there is a problem with = the > XML layer most probably that is in the axis2_parser or Axiom layers. I'm > unaware of a location for libxml2 debug library. The best option may be t= o > build it in Windows. But if you are using Guththila these debugging probl= ems > won't occur as Guththila is part of Axis2/C. > > Supun.. > > > On Mon, Oct 6, 2008 at 6:22 PM, wrote: > >> How can I know what is the problem as you indicated in the mail below? >> >> My guess is that it has to do with the libxml2.dll but where can I find = it >> for debug? >> >> >> >> /Indra >> >> >> ------------------------------ >> >> *From:* Supun Kamburugamuva [mailto:supun06@gmail.com] >> *Sent:* den 6 oktober 2008 11:54 >> *To:* Apache AXIS C Developers List >> *Subject:* Re: Axis2/c debug mode problem >> >> >> >> Please try to build with Guththila and you will be able to know for sure >> what is the cause of the problem. >> >> Supun. >> >> On Mon, Oct 6, 2008 at 2:48 PM, wrote: >> >> I tried to clean and build but I still have the same problem. I checked >> and all the axis-dlls are compiled in debug but I think the problem has = to >> do with my libxml2. Do you know where I can find a libxml2.dll that is >> compiled for debug? >> >> >> >> /Indra >> >> >> ------------------------------ >> >> *From:* Supun Kamburugamuva [mailto:supun06@gmail.com] >> *Sent:* den 4 oktober 2008 06:00 >> *To:* Apache AXIS C Developers List >> *Subject:* Re: Axis2/c debug mode problem >> >> >> >> Usually this happens due to DLL conflicts. Try to clean everything build >> again. I usually clean everything manually and build again when this >> happens. >> >> Supun. >> >> On Fri, Oct 3, 2008 at 7:36 PM, wrote: >> >> Hi again! >> >> I have compiled axis2/c using the axis2c.sln in release mode which works >> fine. >> >> I want to compile it in debug mode but it's not working. I get this erro= r >> message when I debug: >> >> >> >> "Windows has triggered a breakpoint in axis2_http_server.exe. >> >> This may be due to a corruption of the heap, which indicates a bug in >> axis2_http_server.exe or any of the DLLs it has loaded. >> >> This may also be due to the user pressing F12 while axis2_http_server.ex= e >> has focus. >> >> The output window may have more diagnostic information." >> >> >> >> And this when I try to run it: >> >> >> >> "Debug Assertion Failed! >> >> Program: =85s2c-src-1.5.0\ides\axis2c\deploy\bin\axis2_httpserver.exe >> >> File: f:\dd\vctools\crt_bld\self_x86\crt\src\dbgheap.c >> >> Line:1317 >> >> >> >> Expression: _CrtIsValidHeapPointer(pUserData) >> >> >> >> For information on how your program can cause an assertion failure, see >> the Visual C++ documentation on asserts. " >> >> >> >> I have attached a screen shot of the heap=85 >> >> >> >> Can you help me? >> >> >> >> /Indra >> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org >> For additional commands, e-mail: axis-c-dev-help@ws.apache.org >> >> >> >> >> -- >> Software Engineer, WSO2 Inc >> http://wso2.org >> >> >> >> >> -- >> Software Engineer, WSO2 Inc >> http://wso2.org >> > > > > -- > Software Engineer, WSO2 Inc > http://wso2.org > --=20 Software Engineer, WSO2 Inc http://wso2.org ------=_Part_24960_26250688.1223300481312 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
When you use libxml2 you need to define the AXIS2_LIBXML2_= ENABLED pre-processor directive in the axiom project. I think this is the c= ause of this error. I realized this only when I go though the code.

Supun.

On Mon, Oct 6, 2008 at 6:31 PM, Su= pun Kamburugamuva <supun06@gmail.com> wrote:
The chances are very small to a bug like this to be in lib= xml2 as it is a very well tested and widely used XML library. If there is a= problem with the XML layer most probably that is in the axis2_parser or Ax= iom layers. I'm unaware of a location for libxml2 debug library. The be= st option may be to build it in Windows. But if you are using Guththila the= se debugging problems won't occur as Guththila is part of Axis2/C.

Supun..


On Mon, Oct 6, 2008 at 6:22 PM, <indra.sharma@sun= gard.com> wrote:

How can I know what is the problem= as you indicated in the mail below?

My guess is that it has to do with= the libxml2.dll but where can I find it for debug?

 

/Indra

 

From: Su= pun Kamburugamuva [mailto:supun06@gmail.com]

Sent: den 6 oktober 2008 1= 1:54
To:= Apache AXIS C Developers List
Subject: Re: Axis2/c debug= mode problem

 

Please try to build with Guththila and you will be able to know for sure what is the cause of the problem.

Supun.

On Mon, Oct 6, 2008 at 2:48 PM, <indra.sharma@sungard.com> wrote:

I tried to clean and build but I s= till have the same problem. I checked and all the axis-dlls are compiled in debug but I think the probl= em has to do with my libxml2. Do you know where I can find a libxml2.dll that = is compiled for debug?

 

/Indra

 

From: Su= pun Kamburugamuva [mailto:supun06@gmail.com]
Sent: den 4 oktober 2008 0= 6:00
To: Apache AXIS C Developers List
Subject: Re: Axis2/c debug= mode problem

 

Usually this happens due to DLL conflicts= . Try to clean everything build again. I usually clean everything manually and build again when this happens.

Supun.

On Fri, Oct 3, 2008 at 7:36 PM, <indra.sharma@sungard.com> wrote:

Hi again!

I have compiled axis2/c using th= e axis2c.sln in release mode which works fine.

I want to compile it in debug mo= de but it's not working. I get this error message when I debug:

 

"Windows = has triggered a breakpoint in axis2_http_server.exe.

This may be due to a corruption of t= he heap, which indicates a bug in axis2_http_server.exe or any of the DLLs it has loaded.

This may also be due to the user pre= ssing F12 while axis2_http_server.exe has focus.

The output window may have more diag= nostic information."

 

And this when I try to run it:

 

"Debug As= sertion Failed!

Program: =85s2c-src-1.5.0\ides\axis2c\deploy\bin\axis2_httpserver.exe<= /p>

File: f:\dd\vctools\crt_bld\self_x86= \crt\src\dbgheap.c

Line:1317

 

Expression: _CrtIsValidHeapPointer(p= UserData)

 

For information on how your program = can cause an assertion failure, see the Visual C++ documentation on asserts. 

I have attached a screen shot of the heap=85

 

Can you help me?

 

/Indra

 

 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org




--
Software Engineer, WSO2 Inc
http://wso2.org




--
Software Engineer, WSO2 Inc
http://wso2.org




--
Software Engineer, WSO2= Inc
http://wso2.org



--
Software Engineer, WSO2= Inc
http://wso2.org
------=_Part_24960_26250688.1223300481312--