Re: [Cegcc-devel] Fail to compile gdb

2008-09-23 Thread Pedro Alves
On Wednesday 17 September 2008 20:54:27, Pedro Alves wrote: > On Wednesday 17 September 2008 20:14:52, Pawel Veselov wrote: > > I get this every now and then on some "stuck" applications: > > > > Program received signal SIGTRAP, Trace/breakpoint trap. > > 0x8001b6ec in ?? () > > (gdb) where > > #0

Re: [Cegcc-devel] Fail to compile gdb

2008-09-17 Thread Pedro Alves
On Wednesday 17 September 2008 20:14:52, Pawel Veselov wrote: > I get this every now and then on some "stuck" applications: > > Program received signal SIGTRAP, Trace/breakpoint trap. > 0x8001b6ec in ?? () > (gdb) where > #0 0x8001b6ec in ?? () > (gdb) info threads > * 1 Thread 1154900630 0x8001b

Re: [Cegcc-devel] Fail to compile gdb

2008-09-17 Thread Pawel Veselov
I get this every now and then on some "stuck" applications: Program received signal SIGTRAP, Trace/breakpoint trap. 0x8001b6ec in ?? () (gdb) where #0 0x8001b6ec in ?? () (gdb) info threads * 1 Thread 1154900630 0x8001b6ec in ?? () warning: Couldn't restore frame in current thread, at frame 0 0x

Re: [Cegcc-devel] Fail to compile gdb

2008-09-17 Thread Pedro Alves
On Saturday 13 September 2008 05:51:24, Danny Backx wrote: > Are the issues you refer to (can't get info on threads etc) known gdb > issues ? What issues were those exactly? You should be able to list threads, get backtraces, and interrupt the running program with ^C normally. What exactly isn't

Re: [Cegcc-devel] Fail to compile gdb

2008-09-12 Thread Danny Backx
This is different with the arm-mingw32ce target which we should officially switch to. That't how I created the binary version that's on the SF download. No gdb changes required. Are the issues you refer to (can't get info on threads etc) known gdb issues ? Danny On Wed, 2008-09-10 at 15:

Re: [Cegcc-devel] Fail to compile gdb

2008-09-10 Thread Pawel Veselov
Well, I tried to just compile it with gdb-6.8 source tree, but gdb-6.8 doesn't support the cegcc target out of the box (not that it should), I tried figuring out how to patch GDB by looking at diffs from cegcc 6.4 gdb and vanilla 6.8 gdb, but to no success. Building with arm-*-wince platforms excul

Re: [Cegcc-devel] Fail to compile gdb

2008-09-09 Thread Danny Backx
I believe I've seen reports before about our version of gdb and 64-bit systems. It may be a better idea to try and use the latest gdb from the GNU website. As you may have seen from recent posts, it works out of the box with cegcc, so I think we should remove the old gdb from the cegcc source tree

Re: [Cegcc-devel] Fail to compile gdb

2008-09-09 Thread Pawel Veselov
Hi, ok, talking to myself here... It seems that the problem is that the symbol is redefined incompatibly. It's bound to get redefined, as gdb sources include both core windows headers and core native platform headers. Since I'm building on x86_64, the size_t is defined 64 bit in platform headers,

[Cegcc-devel] Fail to compile gdb

2008-09-09 Thread Pawel Veselov
I'm trying to compile gdb from the SVN sources, and am miserably failing there. Any suggestions as to what I might be doing wrong, or what's wrong with my box? It seems that that particular file is supposed to be compiled for the host architecture, but it picks up the linux stdarg.h and windows inc