On 5/21/06, <b class="gmail_sendername">Till Adam</b> <<a href="mailto:adam@kde.org">adam@kde.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Got it, I think. You'll need to add a:<br><br> if ( requestId != httpGetId ) return;<br><br>at the top of:<br><br>void kdeTest::httpRequestFinished(int requestId, bool error)<br><br>setHost() schedules a request, and get() schedules the next one. The
<br>handler is called first for the setHost request, deletes the file<br>pointer, which the following attempt to satisfy the get() request<br>access. Boom.<br><br>Valgrind is a great tool for debugging these kinds of things, btw. It
<br>showed immediately where the illegal memory access was, and where that<br>memory was deleted from.</blockquote><div><br>
Great!! That solved it . <br>
Must really spend more time trying to read how to use Valgrind and more
importantly how to make sense out of backtrace. Any pointers for the
later? :)<br>
</div><br></div>Thanks once again,<br>-- <br>Aditya Mooley<br>=============================================================<br>PHP Applications for E-Biz: <a href="http://www.sanisoft.com">http://www.sanisoft.com</a><br>
Coppermine Picture Gallery: <a href="http://coppermine.sf.net">http://coppermine.sf.net</a><br>Koppermine KDE Client: <a href="http://koppermine.sf.net">http://koppermine.sf.net</a><br>=============================================================