[Bug 13188] command-line kernel debugger kd display problem

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=13188





--- Comment #13 from Yu-Ning Feng <fengyuning1984 at gmail.com>  2008-05-18 04:36:01 ---
(In reply to comment #12)
> Created an attachment (id=13143)
 --> (http://bugs.winehq.org/attachment.cgi?id=13143) [details]
> Patch
> 

Applied to my local tree and tested. Not work as expected. See below.

> In reply to comment #11:
> - the start position of the edition is never changed (in windows). Using a
> simple test program that replicates what it's described in this PR (one thread
> reading a string on console, a second one calling WriteConsole), it's clear
> that the start position is not changed (e.g. using <home> key brings back the
> cursor to its initial position)

I see. However, it is(seems) not true. I verified just now in my Windows xp
sp2(host, target is another machine also running xp). Here is a kd session:

(copyright messages)

Opened \\.\com1
Waiting to reconnect...
verConnected to Windows XP 2600 x86 compatible target, ptr64 FALSE
~~~
(...)
kd> command
    ^
I input 'ver' before connect, and 'command' after being prompted. Then, <home>
hit and the cursor is at where '^' indicates. As you can see, start position is
changed. If not, 'ver' would have been echo'ed before copyright messages, which
is the behavior of original code. I have tried that, with your patch applied,
'ver' and 'command' appear at the right place, but after <home> hit, the cursor
is at the very beginning, as you would expect.

> - you can switch to the emacs emulation mode by right-clicking in the
> wineconsole window (if you're using the user backend)
> 

I was in emacs mode. Most keys work, say, C-a, C-e, C-k, M-d etc., but not
M-<backspace>. Anyway, I cannot help to say I like this emacs mode feature very
much.

> let me know if the attached patch fixes your issues.
> 

Hope you can confirm what I have described above.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.