* [gdb6.6/6.7] undefined/not implemented MI command causes gdb crash (windows/linux)
@ 2007-10-15 14:11 Bogdan Slusarczyk
0 siblings, 0 replies; 4+ messages in thread
From: Bogdan Slusarczyk @ 2007-10-15 14:11 UTC (permalink / raw)
To: gdb
Hi, I have annoying problem with gdb6.6/6.7. I run 'gdb -i mi', and type
'dummy' (is not defined) alternately with '-target-attach' (is not
implemented). I get gdb crash each time (with others not defined/not
implemented commands too). Can you reproduce this problem?
Regards
Bogdan
PS. I tried gdb6.3 - it's ok.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gdb6.6/6.7] undefined/not implemented MI command causes gdb crash (windows/linux)
@ 2007-10-15 14:13 Bogdan Slusarczyk
2007-10-15 15:00 ` Daniel Jacobowitz
0 siblings, 1 reply; 4+ messages in thread
From: Bogdan Slusarczyk @ 2007-10-15 14:13 UTC (permalink / raw)
To: gdb
Hi, I have annoying problem with gdb6.6/6.7. I run 'gdb -i mi', and type
for example 'dummy' (is not defined) alternately with '-target-attach'
(is not implemented). I get gdb crash each time (with others not
defined/not implemented commands too). Can you reproduce this problem?
Regards
Bogdan
PS. I've tried gdb6.3 - it's ok.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gdb6.6/6.7] undefined/not implemented MI command causes gdb crash (windows/linux)
2007-10-15 14:13 Bogdan Slusarczyk
@ 2007-10-15 15:00 ` Daniel Jacobowitz
2007-10-16 7:17 ` Bogdan Slusarczyk
0 siblings, 1 reply; 4+ messages in thread
From: Daniel Jacobowitz @ 2007-10-15 15:00 UTC (permalink / raw)
To: Bogdan Slusarczyk; +Cc: gdb
On Mon, Oct 15, 2007 at 04:13:34PM +0200, Bogdan Slusarczyk wrote:
> Hi, I have annoying problem with gdb6.6/6.7. I run 'gdb -i mi', and type for
> example 'dummy' (is not defined) alternately with '-target-attach' (is not
> implemented). I get gdb crash each time (with others not defined/not
> implemented commands too). Can you reproduce this problem?
Could you be more precise?
- What target is GDB configured for?
- What exactly do you type, and what does GDB do?
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gdb6.6/6.7] undefined/not implemented MI command causes gdb crash (windows/linux)
2007-10-15 15:00 ` Daniel Jacobowitz
@ 2007-10-16 7:17 ` Bogdan Slusarczyk
0 siblings, 0 replies; 4+ messages in thread
From: Bogdan Slusarczyk @ 2007-10-16 7:17 UTC (permalink / raw)
To: gdb
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-10-16 7:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-10-15 14:11 [gdb6.6/6.7] undefined/not implemented MI command causes gdb crash (windows/linux) Bogdan Slusarczyk
2007-10-15 14:13 Bogdan Slusarczyk
2007-10-15 15:00 ` Daniel Jacobowitz
2007-10-16 7:17 ` Bogdan Slusarczyk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox