Stupid Winedbg question

[Bobby Bingham]

Ok, I feel like an idiot for having to ask this, but it's my first time 
realing using the debugger.  When wine starts the debugger on an exception, 
it opens it up in another xterm.  Is there an easy way to copy it's output?  
The usual select and middle-click isn't working because it doesn't let me 
select the text to begin with.

Thanks in advance for your patience.

Bobby Bingham

[James Hatheway]

> Ok, I feel like an idiot for having to ask this, but it's my first time 
> realing using the debugger.  When wine starts the debugger on an exception, 
> it opens it up in another xterm.  Is there an easy way to copy it's output?  
> The usual select and middle-click isn't working because it doesn't let me 
> select the text to begin with.

Hold the Shift key while selecting the text.  Or, in your ~/.wine/user.reg
change the [Software\Wine\WineDbg] UseXTerm key from 01 to 00.
I find that is more useful so that all the output can be put into a file
for later perusal. (ie. I usually run the debugger with:
./debugger/winedbg 2>&1 | tee output.log)

-James

[Dan Kegel]

Bobby Bingham wrote:
> Ok, I feel like an idiot for having to ask this, but it's my first time
> realing using the debugger.  When wine starts the debugger on an exception,
> it opens it up in another xterm.  Is there an easy way to copy it's output?
> The usual select and middle-click isn't working because it doesn't let me
> select the text to begin with.

I had the same problem, and I was highly annoyed at winedbg
for not allowing cut and paste or any sort of session logging.
- Dan