Re: [gdb6.6/6.7] undefined/not implemented MI command causes gdb crash (windows/linux)

[Bogdan Slusarczyk <bodzio131 at op dot pl>]

> Could you be more precise?
>
> - What target is GDB configured for?

windows(XP): i686-pc-cygwin
linux: i686-pc-linux-gnu

I tried also i686-pc-mingw32 (using mingw gdb6.6 source pack), but this 
one it's ok (except it hangs after 'attach' command, so it's useless for 
me) I noticed that mingw version intercepts user input from shell with 
bit different way. I don't know how to explain it, just run windows 
shell with gdb and try use 'up/down' keys.

> - What exactly do you type, and what does GDB do?

on both platforms run gdb using: 'gdb -i mi' and:

windows:
dummy
&"dummy\n"
&"Undefined command: \"dummy\".  Try \"help\".\n"
^error,msg="Undefined command: \"dummy\".  Try \"help\"."
(gdb)
-target-attach
^error,msg="Undefined mi command: target-attach (missing implementation)"
^error,msg="  12118 [sig] gdb 3968 open_stackdumpfile: Dumping stack 
trace to gdb.exe.stackdump

linux:
dummy
&"dummy\n"
&"Undefined command: \"dummy\".  Try \"help\".\n"
^error,msg="Undefined command: \"dummy\".  Try \"help\"."
(gdb)
-target-attach
^error,msg="Undefined mi command: target-attach (missing implementation)"
^error,msg=""
(gdb)
dummy
&"dummy\n"
Segmentation fault


Regards
Bogdan