Mike Hearn wrote:
> FWIW I usually find +all traces give too much output for debugging
> anything other than startup problems where you have no idea what's
> wrong. Beyond a few seconds execution the logs get too big to work with,
> especially if you're working blind.
And also, as I reported on bug
James Hawkins wrote:
Oh ok thanks Rob I'll try it out.
I tend to find piping stuff through sed is too slow (but then I have
quite a slow computer). There is a patch floating around in the archives
that lets you toggle debug logging on and off using the F12 key. It
works at the level of the debug
Oh ok thanks Rob I'll try it out.
On Thu, 26 Aug 2004 01:49:41 +0100, Robert Shearman <[EMAIL PROTECTED]> wrote:
> James Hawkins wrote:
>
> >I ran WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
> >in the terminal, and all of the debug output is being displayed
> >already without
James Hawkins wrote:
I ran WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
in the terminal, and all of the debug output is being displayed
already without selecting the "Put..log" option. I switched
"Managed" to "N" at Vincent's suggestion. Any ideas?
Try this instead:
WINEDEB
I ran WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
in the terminal, and all of the debug output is being displayed
already without selecting the "Put..log" option. I switched
"Managed" to "N" at Vincent's suggestion. Any ideas?
On Wed, 25 Aug 2004 19:34:34 -0400, James Hawkin
Vincent Béron wrote:
> I didn't see it when used in "Managed"="Y" mode, but with "Managed"="N"
> the option's there (Alt-space, or the icon in the top-left corner of the
> window of the app).
When an app is running in Managed Mode we can access the system menu opening
the first menu (usually File)
Oh ok thanks a bunch I will definitely try it out now.
On 25 Aug 2004 19:25:19 -0400, Vincent Béron
<[EMAIL PROTECTED]> wrote:
> Le mer 25/08/2004 à 19:11, James Hawkins a écrit :
> > > > Then you just need to bring the system menu up and click on "Put 'Debug
> > > > mark' in debug log" and debugg
Le mer 25/08/2004 à 19:11, James Hawkins a écrit :
> > > Then you just need to bring the system menu up and click on "Put 'Debug
> > > mark' in debug log" and debugging will then start.
>
> I'm not exactly sure what you mean by system menu. I cant remember
> seeing the "Put...log" anywhere. Than
> > Then you just need to bring the system menu up and click on "Put 'Debug
> > mark' in debug log" and debugging will then start.
I'm not exactly sure what you mean by system menu. I cant remember
seeing the "Put...log" anywhere. Thankyou for your help on this
response btw.
On 25 Aug 2004 18:4
Le mer 25/08/2004 à 17:29, Robert Shearman a écrit :
> James Hawkins wrote:
>
> >Hi,
> >
> >Is there a way to change the trace options of WINEDEBUG during
> >runtime?
> >
> WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
>
> Then you just need to bring the system menu up and
James Hawkins wrote:
Hi,
Is there a way to change the trace options of WINEDEBUG during
runtime?
WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
Then you just need to bring the system menu up and click on "Put 'Debug
mark' in debug log" and debugging will then start. I seem t
Hi,
Is there a way to change the trace options of WINEDEBUG during
runtime? For example, let's say I'm running an installer that
encounters a fatal error during one part of the install. I'm not
exactly sure where in the wine code base this error is occurring and
it would take forever if I se
12 matches
Mail list logo
