[ros-dev] [ros-diffs] [fireball] 50967: - Revert 47615. Please fix actual sysreg instead of adding inconsistency between 1st, 2nd and 3rd stages debugging connections. This should fix sysreg3's inability to do backtrace...

[Timo Kreuzer]

Am 05.03.2011 10:03, schrieb Aleksey Bragin:
> Yes, throughout all years I used to type into the virtual machine 
> window (or real hardware's keyboard) in order to enter kdbg commands 
> in 1st, 2nd and 3rd stages. The default way for 2nd and 3rd remains 
> the same, but that commit changed default for the 1st stage, and that 
> was quite unexpected (there was even a bug report submitted for that). 
> Not to say that I didn't notice that commit back then, and was 
> wondering why sysreg3 is not able to enter any kdbg commands into 
> virtual box window when first stage of setup runs.
>
>
> On Mar 5, 2011, at 4:34 AM, Olaf Siejka wrote:
>
>> It causes issues in 1st stage access to kdbg. Simply speaking, 
>> instead of using vbox window focus to type in kdbg commands, those 
>> only work with terminal (like putty) window focus.
>>

I don't consider this an "issue". Its normal behaviour and the way 
RosDbg works and sysreg as well (iirc) and I am used to work with it 
since ages, because it simply sucks to focus one window and have the 
text in another. If something is inconsistent here, then sysreg, using 
VBox window focus in 1st stage and serial in 2nd and 3rd stage. Or does 
the new sysreg suddenly use the window focus everywhere? Or only the one 
for windows while the one on linux still uses serial? That's again 
inconsistency. And please don't mistake your personal preference with 
consistency, for me and everyone using RosDbg its more consistent with 
kdserial :)

Timo