gdb remote debugging with threads

gdb remote debugging with threads

[Peter Choi]

Hi,

  Excuse me. I know GDB should have supported remote
debugging with multi-threads, but I still encounter
problem.

  I'm using GDB 6.3 (host=target=i686),

case (1):
   I compile my program with shared library. 
   To make the environment simple, I make the host
computer and target computer two identical platform
(ie. same i686 cpu and same library path).

  But when I run remote debugging, the following are
reported:
  On the host computer running GDB, it reported:
"warning: .dynamic section for "/lib/ld-linux.so.2" is
not at the expected address.

  and when I use "info threads", I cannot see all
other threads I have created during the execution.

case (2):
  I compile my program  with static library. 
  Still use two identical platform as my host and
target computer.

  But when I run remote debugging, the following are
reported:
  On the target computer side, it reported:
"cannot find new threads: generic error".

  On the host computer side, it reported:
"Ignoring packet error, continuing".

  And again, when I use "info threads", I cannot see
all other threads I have created during the execution.

  Please advise anyone have any idea how to get around
this?????
  Please advise. Thank  you for your attention.


Regards.
Peter Choi


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: gdb remote debugging with threads

[Daniel Jacobowitz]

On Thu, Jun 15, 2006 at 03:21:34AM -0700, Peter Choi wrote:
> Hi,
> 
>   Excuse me. I know GDB should have supported remote
> debugging with multi-threads, but I still encounter
> problem.
> 
>   I'm using GDB 6.3 (host=target=i686),
> 
> case (1):
>    I compile my program with shared library. 
>    To make the environment simple, I make the host
> computer and target computer two identical platform
> (ie. same i686 cpu and same library path).
> 
>   But when I run remote debugging, the following are
> reported:
>   On the host computer running GDB, it reported:
> "warning: .dynamic section for "/lib/ld-linux.so.2" is
> not at the expected address.
> 
>   and when I use "info threads", I cannot see all
> other threads I have created during the execution.

Are you really, really sure that the two computers have the same
libraries?  Use md5sum /lib/ld-linux.so.2 to check.

-- 
Daniel Jacobowitz
CodeSourcery

Re: gdb remote debugging with threads

[Jan Kratochvil]

Dear Daniel,

On Thu, 15 Jun 2006 16:01:28 +0200, Daniel Jacobowitz wrote:
> On Thu, Jun 15, 2006 at 03:21:34AM -0700, Peter Choi wrote:
...
> >   On the host computer running GDB, it reported:
> > "warning: .dynamic section for "/lib/ld-linux.so.2" is
> > not at the expected address.
> > 
> >   and when I use "info threads", I cannot see all
> > other threads I have created during the execution.
> 
> Are you really, really sure that the two computers have the same
> libraries?  Use md5sum /lib/ld-linux.so.2 to check.

couldn't this be from the "prelink" which generally maps the libraries to
different addresses on each machine?


Regards,
Jan

Re: gdb remote debugging with threads

[Daniel Jacobowitz]

On Thu, Jun 15, 2006 at 05:03:27PM +0200, Jan Kratochvil wrote:
> Dear Daniel,
> 
> On Thu, 15 Jun 2006 16:01:28 +0200, Daniel Jacobowitz wrote:
> > On Thu, Jun 15, 2006 at 03:21:34AM -0700, Peter Choi wrote:
> ...
> > >   On the host computer running GDB, it reported:
> > > "warning: .dynamic section for "/lib/ld-linux.so.2" is
> > > not at the expected address.
> > > 
> > >   and when I use "info threads", I cannot see all
> > > other threads I have created during the execution.
> > 
> > Are you really, really sure that the two computers have the same
> > libraries?  Use md5sum /lib/ld-linux.so.2 to check.
> 
> couldn't this be from the "prelink" which generally maps the libraries to
> different addresses on each machine?

It's possible.  I don't know if that would interfere.

-- 
Daniel Jacobowitz
CodeSourcery