Uwe Stöhr wrote:
>> obviously it's no good for SIGSEGV. Perhaps if it had the option to write
>> to a
>> file, it would do.
>
> For this case, use the windows console window, do what you did to crash LyX
> and copy the debug output to a file, or better, paste it directly to a bug
> report.
err
Am 18.11.2010 23:45, schrieb Jim Oldfield:
It's a pity we can't do both/ choose at run time. I'm glad we have Pavel's
suggested method works for most cases (I can't believe I missed that!),
That's why this feature was built in LyX 2.0.
obviously it's no good for SIGSEGV. Perhaps if it had
Thanks for your replies Pavel and Uwe.
Ok, it turns out here is my problem: I was using "dbg=all", but this trace
level
doesn't exist. The one I was after was "any"! I realise others may be more
appropriate, but it doesn't take that long on my computer to start with "any"
and if you can nail
Am 18.11.2010 20:57, schrieb Jim Oldfield:
I am trying to generate debug output in Lyx 2.0.0 beta 1. Using LyxLauncher
seems to capture any output into a console window and throw it away (I assume
that this is because I'm using the alternative installer; normally I'd use the
regula
Jim Oldfield wrote:
> I am trying to generate debug output in Lyx 2.0.0 beta 1. Using LyxLauncher
what about the new feature view->view messages?
pavel
I am trying to generate debug output in Lyx 2.0.0 beta 1. Using LyxLauncher
seems to capture any output into a console window and throw it away (I assume
that this is because I'm using the alternative installer; normally I'd use the
regular one), so I'm trying to run lyx.exe dir
