From: damny@web.de
To: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: build a canadian cross gdb
Date: Mon, 12 Oct 2009 17:56:00 -0000 [thread overview]
Message-ID: <1193752320@web.de> (raw)
> > You are still incorrect. Like I said before, if OpenOCD crashes, the
> > bug is in OpenOCD.
>
> In other words, even if GDB did send something that OpenOCD did not like,
> whether correct or not, OpenOCD should still not crash.
ok ... your partially right, if openocd get a faulty gdb communication, openocd has to catch it.
but ... logical consequences.
=> gdb-6.8.50.20080308-cvs build on windows works with openocd for windows
=> gdb-6.7.50.200080229 (older version than the working one) build on linux for windows doesn't work with openocd for windows
=> gdb-6.8 (the most exact equal version like the working one) build on linux for windows doesn't work with openocd for windows
=> gdb-6.8.50.20090801 (newer version than the working one) build on linux for windows doesn't work with openocd for windows
=> gdb-7.0.50.20090926 (newer version than the working one) build on linux for windows doesn't work with openocd for windows
=> older, nearly exact and newer versions (than the named above) of gdb build on linux for windows doesn't work with openocd for windows
=> openocd online docs say "Use GDB 6.7 or newer with OpenOCD if you run into trouble."
=> it's only a (new) assumption, but i estimate that remote protocol didn't changed so drastic in 6.8.50 versions;
so i think my original used version gdb version (6.8.50.20090801) should work like gdb-6.8.50.20080308-cvs
the main difference between 'working' and 'not working' is the way of the build process, respectively the build system ('windows' <=> 'linux').
my assumption from first post (tui, termcap, ncurses) was highly speculative.
that's why i searched for help.
so i ask again:
has anybody of you experiences in building gdb the way i try it (canadian cross with build=i686-linux-gnu, host=i586-mingw32msvc, target=arm-elf)?
does anybody know if there are gdb patches for canadian cross builds, ...?
and some new questions:
was this actually done before?
is anybody here that know/use openocd and has experiences in the way of communication of openocd and gdb?
thanks again,
daniel
_______________________________________________________________
Neu: WEB.DE DSL bis 50.000 kBit/s und 200,- Euro Startguthaben!
http://produkte.web.de/go/02/
next reply other threads:[~2009-10-12 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 17:56 damny [this message]
2009-10-12 18:02 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 18:22 damny
2009-10-12 18:31 ` Daniel Jacobowitz
2009-10-11 8:43 damny
2009-10-11 13:58 ` Daniel Jacobowitz
2009-10-12 2:52 ` Joel Brobecker
2009-10-06 19:17 damny
2009-10-06 20:43 ` Daniel Jacobowitz
2009-10-06 17:43 damny
2009-10-06 17:56 ` Daniel Jacobowitz
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=1193752320@web.de \
--to=damny@web.de \
--cc=brobecker@adacore.com \
--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