hmmm....thank you
attached the pd.log file and the file pdVV.txt -verbose -verbose prints...
thank you in advance der.brandt
Zitat von "IOhannes m zmoelnig" zmoelnig@iem.at:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-08-29 18:46, brandt@subnet.at wrote:
- what get's printed to the pd-console before the crash? what get's
printed to the console?
nothing....pd just disapear
never!
i think this has been mentioned on this list a couple of times, but let's do it again
you ought to start Pd from the cmdline/shell/CLI (the thing you get when you do "Cmd-R" and start the "cmd" program), use "pd.com" (rather than "pd.exe"), give it the "-stderr" flag (so it won't print to the pd-console but to the console instead), and eventually add "-verbose
- -verbose" to the flags.
something like:
$ C:\Programme\pd\bin\pd.com -stderr -open patch.pd 2> pd.log
this will print everything into a log-file "pd.log". once you triggered the crash, the pd.log will still be their and ready for future inspection.
- what if you raise verbosity to level 2?
i have to find out how, because i am still not familiar with the new .bat in win7
no need for a .bat file. .bat files are their for convenience, so you don't need to reiterate simple tasks. let's hope that you don't need to debug so often, that you need a convenience framework for that.
just add "-verbose -verbose" (that's 2* "-verbose") right after ther "-stderr"...
fgnasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5ci/QACgkQkX2Xpv6ydvTufgCeJO1cfQSgycPUWmAywcspoRBO 7CsAoK5MEuYL2RijYndj5DUflwlFo+VZ =4mkg -----END PGP SIGNATURE-----