Stupid winedbg question

Marcus Meissner marcus at jet.franken.de
Wed May 9 14:42:57 CDT 2001


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




More information about the wine-devel mailing list