Re: Linking problems with gdb-7.2
On Sun, 2011-03-20 at 22:45 +0100, Svante Signell wrote:
> On Sun, 2011-03-20 at 22:21 +0100, Samuel Thibault wrote:
> > Svante Signell, le Sun 20 Mar 2011 22:15:35 +0100, a écrit :
> > > On Sun, 2011-03-20 at 22:09 +0100, Samuel Thibault wrote:
> > > > Svante Signell, le Sun 20 Mar 2011 22:02:35 +0100, a écrit :
> > > > > This function is defined in threads.c bud does not seem to be recognized
> > > > > by the linker. What is the difference with a symbol reported as "T" or
> > > > > "t" ?
> > > >
> > > > t is for static functions, which can't be used outside the .o file. Is
> > > > it hurd-only that we use the prune_threads function?
> > >
> > > I'm not sure, but it looks like it is hurd-only, see
> > > http://sourceware.org/ml/gdb-patches/2009-11/msg00581.html
> > >
> > > How to change the "t" to a "T"?
> >
> > Drop static in the prune_threads() definition.
>
> Thanks, looks promising. Will report later on the outcome.
Finally, it builds!! A little tricky since the build is via autotools
and the current autoconf is later than the one used to create the
configure scripts. It also works, At least I could run random programs
with gdb: mutt+mutt-dbg and ls. It does not show output (as 7.2-1+b1
does):
gdb /bin/ls
Starting program: /bin/ls
Can't fetch registers from thread bogus thread id 1: No such thread
(gdb) quit
A debugging session is active.
Inferior 1 [bogus thread id 0] will be killed.
Patches will be mailed here for review before submitting a bug report.
Reply to: