<p>Cool! I'll try this out and let you know.</p>
<div class="gmail_quote">On Sep 27, 2012 1:33 PM, "Miller Puckette" <<a href="mailto:msp@ucsd.edu">msp@ucsd.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've never done this but perhaps it would work to edit the line in<br>
pd-gui.tcl:<br>
<br>
exec -- $pd_exec -guiport $::port &<br>
<br>
to:<br>
<br>
exec -- $pd_exec -guiport $::port -d 1 >& /tmp/foo &<br>
<br>
(not sure if '>&" or '2>' depending on shell).<br>
<br>
cheers<br>
Miller<br>
<br>
On Thu, Sep 27, 2012 at 01:23:23PM -0400, Ivica Ico Bukvic wrote:<br>
> This is actually on Linux.<br>
><br>
> The problem is likely not in C, since program does start up and creates the<br>
> main Pd window and then hangs during loading of the patch (the patch window<br>
> is created but canvas remains empty and after that nothing responds any<br>
> more). It seems to me this is probably because at some point messages sent<br>
> to tcl/tk over network (from C) get mangled after which gui stops<br>
> responding. I had issues like these before with network externals and solved<br>
> them, but this is the one that I had a hard time weeding out since it is so<br>
> sporadic. For this reason, I would like to somehow output all tcl/tk<br>
> commands that were sent to gui. Any way to do this and send it to a separate<br>
> log file without opening a terminal?<br>
><br>
> > -----Original Message-----<br>
> > From: Miller Puckette [mailto:<a href="mailto:msp@ucsd.edu">msp@ucsd.edu</a>]<br>
> > Sent: Thursday, September 27, 2012 12:27 PM<br>
> > To: Ivica Ico Bukvic<br>
> > Cc: <a href="mailto:pd-list@iem.at">pd-list@iem.at</a><br>
> > Subject: Re: [PD] debugging sporadic hangs at startup<br>
> ><br>
> > On Macintosh I presume...<br>
> ><br>
> > Maybe you can use gdb to 'attach' to the running Pd process, assuming it<br>
> at<br>
> > least gets started up (which I assume it must have in order to start<br>
> loading<br>
> > the patch).<br>
> ><br>
> > cheers<br>
> > Miller<br>
> ><br>
> > On Thu, Sep 27, 2012 at 12:22:57PM -0400, Ivica Ico Bukvic wrote:<br>
> > > All,<br>
> > ><br>
> > ><br>
> > ><br>
> > > I am noticing sporadic GUI freezes when loading complex patches on<br>
> > startup.<br>
> > > How would one go about debugging this when most of such startups<br>
> > > happen by clicking on the app icon (so no access to gdb or console).<br>
> > > Short of changing the app icon to make everyone's apps always start<br>
> > > with gdb, is there a way to redirect debugging output to a file?<br>
> > ><br>
> > ><br>
> > ><br>
> > > On a related matter, any other users noticed these ocassional hangs<br>
> > > when loading a complex patch (the window opens but remains blank and<br>
> > > clicking on any options in the menu does nothing)?<br>
> > ><br>
> ><br>
> > > _______________________________________________<br>
> > > <a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
> > > UNSUBSCRIBE and account-management -><br>
> > > <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
><br>
</blockquote></div>