<div>Thanks Greg for the reply.</div>
<div>I think it might be a bug that has been there all along but it is more devestating in the shared library context. The code is also recursive which does not help!</div>
<div>Could I take this oppurtunity to thank you for the time you have put into Pyrex.</div>
<div>I wouldn't have gotten this far in my project if it wasn't for Pyrex.</div>
<div>I started with Swig but I found the documentation very vague and the python part of Swig hard to use for anything complicated becasue of the poor docs..</div>
<div>Pyrex is a breeze in contrast.</div>
<div>If I mange to find out what the problem is I will let you know...</div>
<div>Its back to ddd ....</div>
<div> </div>
<div>regards</div>
<div> </div>
<div>Anthony Percy<br><br> </div>
<div><span class="gmail_quote">On 11/3/05, <b class="gmail_sendername">Greg Ewing</b> <<a href="mailto:greg.ewing@canterbury.ac.nz">greg.ewing@canterbury.ac.nz</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Anthony Percy wrote:<br><br>> It works fine for 26 calls to the function e.g xltEncPcdata ( .......<br>
> const void pContent, ......) in that the pContent value is say 0x801934.<br>> Then on the 27th call to the same function it has the value say 0x801934<br>> but as soon as the first "{" is passed , e.g
as it enteres the function<br>> body without executing any line, pContent changes to say 0x19 !!!!<br><br>The symptoms you're seeing are probably a result of the<br>heap or stack getting corrupted earlier somehow. This
<br>sort of problem is very common when dealing with C code,<br>and can be very difficult to track down.<br><br>All I can suggest is that you try to narrow your test case<br>down to the simplest thing that causes the problem, and
<br>try enabling and disabling various things to try to get<br>an idea of what might be triggering it -- keeping in<br>mind that the error is probably occurring some time<br>*before* any symptoms become apparent.<br><br>--
<br>Greg Ewing, Computer Science Dept, +--------------------------------------+<br>University of Canterbury, | A citizen of NewZealandCorp, a |<br>Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. |
<br><a href="mailto:greg.ewing@canterbury.ac.nz">greg.ewing@canterbury.ac.nz</a> +--------------------------------------+<br></blockquote></div><br>