* Re: build a canadian cross gdb
@ 2009-10-11 8:43 damny
2009-10-11 13:58 ` Daniel Jacobowitz
0 siblings, 1 reply; 11+ messages in thread
From: damny @ 2009-10-11 8:43 UTC (permalink / raw)
To: drow, gdb
> If OpenOCD crashes, the bug is in OpenOCD. It is probably making a
> bad assumption about the remote protocol and incompatible with newer
> GDB.
hi,
i've done some more tests last time.
the unchanged setup is linux mint, i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) & build=i686-linux-gnu, host=i586-mingw32msvc, target=arm-elf. result was:
gdb-6.7.50.200080229
+ sources downloaded from ftp://sourceware.org/pub/gdb/snapshot/current/
+ openocd crashes
gdb-6.8
+ sources downloaded from www.yagarto.de
+ openocd crashes
gdb-6.8.50.20080308-cvs
+ binary downloaded from www.yagartos.de
+ is configured as "--host=i686-pc-mingw32 --target=arm-elf"
+ wasn't build by a canadian cross but with msys/mingw directly on windows (afaik)
+ openocd works fine
gdb-6.8.50.20090801
+ sources downloaded from ftp://sourceware.org/pub/gdb/snapshot/current/
+ openocd crashes
+ my original trail
gdb-7.0.50.20090926
+ sources downloaded from ftp://sourceware.org/pub/gdb/snapshot/current/
+ openocd crashes
so i'm still sure that openocd isn't the problem.
rather it is a problem of building gdb the special canadian cross i want to do whereby gdb is not 'complete/correct' for target remote actions ... because of missing libs in mingw (e.g. termcap, ncurses).
has anybody of you experiences in building gdb the way i try it?
does anybody know if there are gdb patches for canadian cross builds, ...?
thanks,
daniel
_______________________________________________________________
Neu: WEB.DE DSL bis 50.000 kBit/s und 200,- Euro Startguthaben!
http://produkte.web.de/go/02/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
2009-10-11 8:43 build a canadian cross gdb damny
@ 2009-10-11 13:58 ` Daniel Jacobowitz
2009-10-12 2:52 ` Joel Brobecker
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Jacobowitz @ 2009-10-11 13:58 UTC (permalink / raw)
To: damny; +Cc: gdb
On Sun, Oct 11, 2009 at 10:43:36AM +0200, damny@web.de wrote:
> so i'm still sure that openocd isn't the problem.
> rather it is a problem of building gdb the special canadian cross i want to do whereby gdb is not 'complete/correct' for target remote actions ... because of missing libs in mingw (e.g. termcap, ncurses).
You are still incorrect. Like I said before, if OpenOCD crashes, the
bug is in OpenOCD.
The remote protocol changes over time. Clients are supposed to be
robust against unexpected changes. Something is wrong with OpenOCD.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
2009-10-11 13:58 ` Daniel Jacobowitz
@ 2009-10-12 2:52 ` Joel Brobecker
0 siblings, 0 replies; 11+ messages in thread
From: Joel Brobecker @ 2009-10-12 2:52 UTC (permalink / raw)
To: damny, gdb
> 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.
--
Joel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
2009-10-12 18:22 damny
@ 2009-10-12 18:31 ` Daniel Jacobowitz
0 siblings, 0 replies; 11+ messages in thread
From: Daniel Jacobowitz @ 2009-10-12 18:31 UTC (permalink / raw)
To: damny; +Cc: Joel Brobecker, gdb
On Mon, Oct 12, 2009 at 08:21:55PM +0200, damny@web.de wrote:
> > No patches are necessary. We do this every day.
>
> how?
> what's your 'configure'?
The same as the one you showed.
> do you use additional libs during gdb build with mingw on linux?
We provide the same set of libraries on all hosts - optional
components like libiconv, expat, and Python.
> do you have tested your gdb with openocd?
I don't, but our customers have used OpenOCD successfully.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
@ 2009-10-12 18:22 damny
2009-10-12 18:31 ` Daniel Jacobowitz
0 siblings, 1 reply; 11+ messages in thread
From: damny @ 2009-10-12 18:22 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: Joel Brobecker, gdb
> No patches are necessary. We do this every day.
how?
what's your 'configure'?
do you use additional libs during gdb build with mingw on linux?
do you have tested your gdb with openocd?
thanks,
daniel
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
2009-10-12 17:56 damny
@ 2009-10-12 18:02 ` Daniel Jacobowitz
0 siblings, 0 replies; 11+ messages in thread
From: Daniel Jacobowitz @ 2009-10-12 18:02 UTC (permalink / raw)
To: damny; +Cc: Joel Brobecker, gdb
On Mon, Oct 12, 2009 at 07:56:00PM +0200, damny@web.de wrote:
> => it's only a (new) assumption, but i estimate that remote protocol didn't changed so drastic in 6.8.50 versions;
That's incorrect.
> 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, ...?
No patches are necessary. We do this every day.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
@ 2009-10-12 17:56 damny
2009-10-12 18:02 ` Daniel Jacobowitz
0 siblings, 1 reply; 11+ messages in thread
From: damny @ 2009-10-12 17:56 UTC (permalink / raw)
To: Joel Brobecker, gdb
> > 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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
2009-10-06 19:17 damny
@ 2009-10-06 20:43 ` Daniel Jacobowitz
0 siblings, 0 replies; 11+ messages in thread
From: Daniel Jacobowitz @ 2009-10-06 20:43 UTC (permalink / raw)
To: damny; +Cc: gdb
On Tue, Oct 06, 2009 at 09:17:08PM +0200, damny@web.de wrote:
> thanks for the reply.
> but if i use a other gdb (e.g. http://www.yagarto.de/) openocd works fine.
If OpenOCD crashes, the bug is in OpenOCD. It is probably making a
bad assumption about the remote protocol and incompatible with newer
GDB.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
@ 2009-10-06 19:17 damny
2009-10-06 20:43 ` Daniel Jacobowitz
0 siblings, 1 reply; 11+ messages in thread
From: damny @ 2009-10-06 19:17 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: gdb
> > servus,
> >
> > for some time i try to build a canadian cross gdb for myself.
> > the setup is linux mint, i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) & build=i686-linux-gnu, host=i586-mingw32msvc, target=arm-elf.
> > problem is, that the build process produces a windows executable *gdb.exe file, but remote connection to open on-chip debugger (openocd; http://openocd.berlios.de/web/) fails in a way that openocd crashes.
>
> This will have nothing to do with TUI or curses. If openocd crashes
> during the connection, the bug is in openocd.
hi,
thanks for the reply.
but if i use a other gdb (e.g. http://www.yagarto.de/) openocd works fine.
daniel
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: build a canadian cross gdb
2009-10-06 17:43 damny
@ 2009-10-06 17:56 ` Daniel Jacobowitz
0 siblings, 0 replies; 11+ messages in thread
From: Daniel Jacobowitz @ 2009-10-06 17:56 UTC (permalink / raw)
To: damny; +Cc: gdb
On Tue, Oct 06, 2009 at 07:42:53PM +0200, damny@web.de wrote:
> servus,
>
> for some time i try to build a canadian cross gdb for myself.
> the setup is linux mint, i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) & build=i686-linux-gnu, host=i586-mingw32msvc, target=arm-elf.
> problem is, that the build process produces a windows executable *gdb.exe file, but remote connection to open on-chip debugger (openocd; http://openocd.berlios.de/web/) fails in a way that openocd crashes.
This will have nothing to do with TUI or curses. If openocd crashes
during the connection, the bug is in openocd.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 11+ messages in thread
* build a canadian cross gdb
@ 2009-10-06 17:43 damny
2009-10-06 17:56 ` Daniel Jacobowitz
0 siblings, 1 reply; 11+ messages in thread
From: damny @ 2009-10-06 17:43 UTC (permalink / raw)
To: gdb
[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]
servus,
for some time i try to build a canadian cross gdb for myself.
the setup is linux mint, i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) & build=i686-linux-gnu, host=i586-mingw32msvc, target=arm-elf.
problem is, that the build process produces a windows executable *gdb.exe file, but remote connection to open on-chip debugger (openocd; http://openocd.berlios.de/web/) fails in a way that openocd crashes.
my assumption is, that there are inconsistencies regarding to tui (text user interface). this is because of 'make all' messages
>>> snip begin
checking termcap.h usability... no
checking termcap.h presence... no
checking for termcap.h... no
checking for tgetent... no
checking for tgetent in -ltermcap... no
checking for tgetent in -ltinfo... no
checking for tgetent in -lcurses... no
checking for tgetent in -lncurses... no
checking which library has the termcap functions... using gnutermcap
configure: WARNING: no enhanced curses library found; disabling TUI
checking for library containing tgetent... (cached) none required
checking curses.h usability... no
checking curses.h presence... no
checking for curses.h... no
checking cursesX.h usability... no
checking cursesX.h presence... no
checking for cursesX.h... no
checking ncurses.h usability... no
checking ncurses.h presence... no
checking for ncurses.h... no
checking ncurses/ncurses.h usability... no
checking ncurses/ncurses.h presence... no
checking for ncurses/ncurses.h... no
checking ncurses/term.h usability... no
checking ncurses/term.h presence... no
checking for ncurses/term.h... no
checking for term.h... no
>>> snip end
can anyone of you give me some hints?
how to integrate 'termcap' and/or 'ncurses' into mingw? in synaptic i've found no possibility. and a simple copy&paste of 'termcap.h' and 'libtermcap.a' (http://ftp.gnu.org/gnu/termcap/) into mingw include and lib directory wasn't sucessfully, too.
many thanks and greetz,
daniel
________________________________________________________________
Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate
für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/02/
[-- Attachment #2: buildlogs.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 20573 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2009-10-12 18:31 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-11 8:43 build a canadian cross gdb damny
2009-10-11 13:58 ` Daniel Jacobowitz
2009-10-12 2:52 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 18:22 damny
2009-10-12 18:31 ` Daniel Jacobowitz
2009-10-12 17:56 damny
2009-10-12 18:02 ` Daniel Jacobowitz
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox