Hello, Now there shouldn't be this timeout issue - I spawn new erlang process to collect trace data so stop function returns immediately. But when tracing many traces will be generated by dbg. I think that they shouldn't be shown as they just obfuscate results instead of giving any useful information about application. I'm working on starting tracing from different node and I'd like to know how can I create it? I suppose that it should be done using BackendManager rather than by OtpNode constructor. But what arguments should I pass to createBackend function (especially launch parameter) to get node on which I could start tracing? regards, Piotrek
----- Original Message ----- From: "Vlad Dumitrescu" <[email protected]> To: "Piotr Dorobisz" <[email protected]> Cc: "erlide-devel" <[email protected]> Sent: Wednesday, August 11, 2010 2:56:19 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [Erlide-devel] Integrating tracing tool with erlide On Wed, Aug 11, 2010 at 15:46, Piotr Dorobisz <[email protected]> wrote: > It's really strange that you're still getting this problem. Can you write me > what exactly have you done, what settings etc? I forgot to mention that if > you want to trace function calls you should check "call" flag in "Processes" > tab (maybe that's the issue?). I found the problem: if there are many trace messages, there's a timeout: 15:53:54,384 S: (TtbBackend.java:145) : Could not stop tracing tool: org.erlide.jinterface.rpc.RpcTimeoutException: timeout in ttb_integration:stop/1 regards, Vlad ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Erlide-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/erlide-devel
