Re: [Ltib] Re: Can't build both cross-gdb and gdb-server for target?

[Stuart Hughes]

Grant Edwards wrote:
> On Fri, Jun 19, 2009 at 10:31:50AM -0500, Grant Edwards wrote:
>
> > I'm trying to build a gdb server for the target and a cross
> > gdb for the development host (so I have something to use with
> > the gdb-server).  But LTIB won't let me build both a host
> > cross-gdb and a target gdb-server.  Since neither is useful
> > without the other, why can't I build both?
> >
> > What am I supposed to do with gdb-server if I don't have a
> > corresponding cross-gdb for the development host?  Likewise,
> > what am I supposed to do with a cross-gdb if the target has no
> > gdb-server?
>
> I guess you just have to build once with the host cross-gdb
> selected and then a second time with target gdb-server
> selected.  That doesn't really make sense to me. I don't see
> why they can't be built at the same time -- they should be
> separate packages, not different "versions" of a single
> package.
>
> Now that I've gotten both of them built, I can't seem to get
> them to work when debugging a multi-threaded applications.  I
> can "next" through main() as it starts up the threads, but
> after that, gdb has no clue what's going on. Gdb only shows 1
> thread, and when I stop the program, gdb seems clueless about
> what is running.  All it displays is "0xNNNNNNNN in ()?".
>
> When I debug the exact same program on IA32, gdb knows about
> all of the threads, and it can switch to and display
> information about each of the threads.
>
> Is thread debugging not supported on PPC?

Hi Grant,

You can built cross-gdb/gdbserver at the same time (incantation).  Make 
sure you have the following selections when you run ./ltib -m config:

[*] gdb
[ ]   gdb to run natively on the target
[*]   cross gdb (runs on build machine)
[ ]     XML support
---   gdbserver to run natively on the target

Selecting 'cross gdb' forces the selection of gdbserver (that's what the 
--- means).

So far as running gdb goes, you need to send a test case and details for 
the target and version of LTIB you're using.  If this is a Freescale BSP 
you may need to get support from them as it could well be a BSP specific 
problem (gdb thread debugging has worked in the past).

Regards, Stuart