Stupid winedbg question

[Francois Gouget]

This is probably a stupid question but I did not find the answer in
the doc (Wine Developper's Guide).

How do I copy-paste something from winedbg?

A backtrace for instance. Or how do I copy/paste anything to/from any
console application for that matter.

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
                Linux: It is now safe to turn on your computer.

[Ian Pilcher]

Francois Gouget wrote:
> A backtrace for instance. Or how do I copy/paste anything to/from any
> console application for that matter.

Select the text you want to copy and click with your middle mouse button
(mouse button 2) wherever you want to paste it.

[Francois Gouget]

On Tue, 8 May 2001, Ian Pilcher wrote:
> Francois Gouget wrote:
> > A backtrace for instance. Or how do I copy/paste anything to/from any
> > console application for that matter.
>
> Select the text you want to copy and click with your middle mouse button
> (mouse button 2) wherever you want to paste it.

Nope. I tried that, of course, and it doesn't work.

More context:

Winedbg is configured to open a new xterm, and it gives it a title of
'Wine console'.
   But if I try to select text like you would do with any
self-respecting xterm, nothing happens:
 - the text is not highlighted in any way
 - the clipboard is not modified

The same goes if I select something in an xterm and try to paste it
in winedbg. I can click with the middle mouse button all I want, no text
appears in the 'Wine console'.

There's another anomaly. When winedbg is started via the
'just-in-time' debugging feature
 - it displays all lines in a stair-case fashion. It's as if it was
missing a CR (no, I cannot copy/paste an example).
 - The 'Enter' key does not work. All other keys seem to work
fine. I can type 'b', I can use backspace to erase it and type 'quit'
instead. But typeing 'Enter' has no effect. Pretty limiting.

Here is what I have in 'user.reg':

[HKEY_CURRENT_USER\Wine\WineDbg] 973626765

[Software\Wine\WineDbg] 988436772
"BreakAllThreadsStartup"=dword:00000000
"BreakOnAttach"=dword:00000000
"BreakOnCritSectTimeOut"=dword:00000001
"BreakOnDllLoad"=dword:00000000
"BreakOnFirstChance"=dword:00000001
"ConChannelMask"=dword:00000001
"ExtDbgOnInvalidAddress"=dword:00000000
"StdChannelMask"=dword:00000000
"UseXTerm"=dword:00000001

I'm running Debian testing, xterm: 4.0.2-13 (same for all the other X
packages), and I'm using wine from CVS (but older versions have the same
problem)

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
                      Computers are like airconditioners
                They stop working properly if you open WINDOWS

[eric pouech]

> There's another anomaly. When winedbg is started via the
> 'just-in-time' debugging feature
> - it displays all lines in a stair-case fashion. It's as if it was
>
> missing a CR (no, I cannot copy/paste an example).
> - The 'Enter' key does not work. All other keys seem to work
>
> fine. I can type 'b', I can use backspace to erase it and type 'quit'
> instead. But typeing 'Enter' has no effect. Pretty limiting.

sounds more like a strange xterm behavior; may be the xterm, while
started
this way looks for a wrong termcap entry... could you check which value 
has the TERM environment variable when the xterm is started (TRACE("%s",
getenv("TERM"))
in win32/console.c after the fork ?
this may help figuring this out

A+

[Marcus Meissner]

On Wed, May 09, 2001 at 08:37:10PM +0200, eric pouech wrote:
> > There's another anomaly. When winedbg is started via the
> > 'just-in-time' debugging feature
> > - it displays all lines in a stair-case fashion. It's as if it was
> >
> > missing a CR (no, I cannot copy/paste an example).
> > - The 'Enter' key does not work. All other keys seem to work
> >
> > fine. I can type 'b', I can use backspace to erase it and type 'quit'
> > instead. But typeing 'Enter' has no effect. Pretty limiting.
>
> sounds more like a strange xterm behavior; may be the xterm, while
> started
> this way looks for a wrong termcap entry... could you check which value 
> has the TERM environment variable when the xterm is started (TRACE("%s",
> getenv("TERM"))
> in win32/console.c after the fork ?
> this may help figuring this out

No the problem is that I enable Mouse Input in the Win32 Console, which
disallows Cut & Paste.

You can enable cut & paste by pressing NumLock usually.

Ciao, Marcus

[Francois Gouget]

On Wed, 9 May 2001, Marcus Meissner wrote:
> On Wed, May 09, 2001 at 08:37:10PM +0200, eric pouech wrote:
> > > There's another anomaly. When winedbg is started via the
> > > 'just-in-time' debugging feature
> > > - it displays all lines in a stair-case fashion. It's as if it was
> > >
> > > missing a CR (no, I cannot copy/paste an example).
> > > - The 'Enter' key does not work. All other keys seem to work
> > >
> > > fine. I can type 'b', I can use backspace to erase it and type 'quit'
> > > instead. But typeing 'Enter' has no effect. Pretty limiting.
> >
> > sounds more like a strange xterm behavior; may be the xterm, while
> > started
> > this way looks for a wrong termcap entry... could you check which value 
> > has the TERM environment variable when the xterm is started (TRACE("%s",
> > getenv("TERM"))
> > in win32/console.c after the fork ?
> > this may help figuring this out
>
> No the problem is that I enable Mouse Input in the Win32 Console, which
> disallows Cut & Paste.

I think Eric meant it for the staircase effect and Enter not
working. I'll try to dump the TERM value if I can reproduce the
problem. As often as not the debugger does not start at all because I
get into an infinite loop in the SEH handling.

So this tells me that cut&paste is implemented with a Win95-like
interface rather than the much better NT user interface.
   In Win95 you have to click on a button to be allowed to select stuff
and another to copy, and yet another to paste. In NT a right-click +
drag will select stuff. Another right-click will copy it, and a
right-click will paste the contents of the clipboard.
  In any case there's a documentation issue (surprise, surprise)...
> You can enable cut & paste by pressing NumLock usually.

NumLock has no effect on cut&paste on my machine (but my window
manager does not like it).

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
                      Computers are like airconditioners
                They stop working properly if you open WINDOWS

[eric pouech]

> How do I copy-paste something from winedbg?
>
> A backtrace for instance. Or how do I copy/paste anything to/from any
> console application for that matter.

well, there are different behaviors based on your xterm conf
- holding the shift key while selecting the area may work
- there was another trick, using the print screen key (but it no longer
works on my latest Xterm...)

another solution is to set the debugger variable StdChannelMask to 1 (or
the same value as ConChannelMask), you'll get everything on the starting
console

HTH

A+