From: Bogdan Slusarczyk <bodzio131@op.pl>
To: gdb@sourceware.org
Subject: Re: [gdb6.6/6.7] undefined/not implemented MI command causes gdb crash (windows/linux)
Date: Tue, 16 Oct 2007 07:17:00 -0000 [thread overview]
Message-ID: <4714656F.4040008@op.pl> (raw)
In-Reply-To: <20071015145956.GA21761@caradoc.them.org>
> 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
next prev parent reply other threads:[~2007-10-16 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 14:13 Bogdan Slusarczyk
2007-10-15 15:00 ` Daniel Jacobowitz
2007-10-16 7:17 ` Bogdan Slusarczyk [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-15 14:11 Bogdan Slusarczyk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4714656F.4040008@op.pl \
--to=bodzio131@op.pl \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox