Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (athena.apache.org: domain of carl.lefrancois@gmail.com
 designates 216.239.58.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=PxhqMQZ5nNGJvuGRRcOw8pv5FZI45Ay58PSFZGCmmGL7bvbBuIgoaJBu59LYbGoz1jNVco/lKD7PLZYY3mscY59RKKGDrgJC/djAPQ6Or+vWt3x1+lotVgAzbEQKScyQuN7wemf2ltnMrnQl9oex6zlDHocl09IOKsM4uhjeie0=
Message-ID: <5f77498f0802221230i20e2d1e2w92d6648a1745c0a6@mail.gmail.com>
Date: Fri, 22 Feb 2008 15:30:27 -0500
From: "=?ISO-8859-1?Q?Carl_Lefran=E7ois?=" <carl.lefrancois@gmail.com>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Subject: [AXIS2C] trouble debugging under windows
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1273_18205858.1203712227781"

------=_Part_1273_18205858.1203712227781
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

For several days I have been struggling to enable line by line debugging in
visual C 6.0.

An example of the problem is that while stepping through code, when
attempting to step into a call to the client API, the debugger shows the
wrong lines of code and wrong call stack.

steps taken to resolve:

-make sure all modules are compiled with the same compiler and linker
options
-create new workspaces for each module
-take options directly from makefile provided in /build/win32
-replace LF line endings with windows-style CRLF line endings in .c and .h
sources (supposed to affect C preprocessor line count)

so far in all cases the behaviour is the same: I can step through my code
but not into any client API DLLs.

My hope in sending this message is that someone using the same environment
can confirm they are able to debug properly in client API DLLs (or any Axis2
DLL for that matter).

So far aside from work environment compatibility problems, the experience
with Axis2C is very positive.

Thanks in advance for any advice you may give me!
Carl

------=_Part_1273_18205858.1203712227781
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

For several days I have been struggling to enable line by line debugging in visual C 6.0.<br><br>An example of the problem is that while stepping through code, when attempting to step into a call to the client API, the debugger shows the wrong lines of code and wrong call stack.<br>
<br>steps taken to resolve: <br><br>-make sure all modules are compiled with the same compiler and linker options<br>-create new workspaces for each module<br>
-take options directly from makefile provided in /build/win32<br>-replace LF line endings with windows-style CRLF line endings in .c and .h sources (supposed to affect C preprocessor line count)<br><br>so far in all cases the behaviour is the same: I can step through my code but not into any client API DLLs.<br>
<br>My hope in sending this message is that someone using the same environment can confirm they are able to debug properly in client API DLLs (or any Axis2 DLL for that matter).<br><br>So far aside from work environment compatibility problems, the experience with Axis2C is very positive.<br>
<br>Thanks in advance for any advice you may give me!<br>Carl<br>

------=_Part_1273_18205858.1203712227781--