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