On Sep 26, 10:15 am, Christian Biesinger <[EMAIL PROTECTED]> wrote: > Diaa wrote: > > Do you have any ideas that help me understand what's wrong? may be > > using a debug firefox executable can help(though the amount of source- > > code is huge), What do you think? > > Yeah, in a debug build (or, in fact, if you use Windows you can use the > symbol server > -http://developer.mozilla.org/en/docs/Using_the_Mozilla_symbol_server) > you could set a breakpoint in yourchannel::AsyncOpen and see where that > was called from. That should help figuring out why it happens. > > -christian > > -- > All the world's a stage, > And all the men and women merely players: > They have their exits and their entrances; > And one man in his time plays many parts, [...] --W. Shakespeare
Thanks again for your help, the symbol server is a very good facility that saves the trouble/time compiling firefox. I found out what the problem is, it was memory corruption, I should have known that because usually it's only memory corruption that can does such sorts of magic, but what's strange is that the application didn't crash. Well anyway, now I'm on my way back continuing the development of the protocol handler and I have some questions: is nsIRequest::Cancel() synchronous or asynchronous? if it's async, how to notify the host that I've finished cleaning up? Which values are allowed to be returned from nsIRequest::GetStatus()? Regards, Diaa Sami _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
