Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mangesh Edake <m_edake@yahoo.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Kaushik karandikar <kaushikkarandikar@yahoo.com>,
	gdb <gdb@sourceware.org>
Subject: Re: gdbserver + arm nommu
Date: Tue, 05 Dec 2006 12:01:00 -0000	[thread overview]
Message-ID: <20061205120058.3723.qmail@web50502.mail.yahoo.com> (raw)
In-Reply-To: <20061118163128.GA14647@nevyn.them.org>

Hi all,
  I am able to debug a program using gdb-6.4 and
gdb-6.4/gdbserver. Many thanks to Daniel for his
precious suggestions.
  Currently I am trying to debug a multi-threaded
program using the same gdbserver. I have compiled
uClibc with the pThread debugging enabled and then 
statically linked gdbserver with libthread_db.a 
and the program with libpthread.a, as my target
doesn't support dynamic linking (no shared lib
support, even toolchain cannot create .so files). 
  Now when I try to debug a program, it kills at 
'pthread_create' line. Between 'info th' from the gdb
running on host lists only the main process as a
thread. I checked with gdbserver and it supports many
of the q-packets and thread related packets.
  In this case gdb at host is supposed to refer the
exactly same 'pthread symbols' as target is, but it
cannot. Even I cannot try solib-absolute-prefix  
or solib-search-path, since there are no corresponding
.so (libthread_db.so) files generated at host. Hence
looking at the scenario, is this causing my program to
terminate? and is there any way to tell gdb the
'pthread symbols' statically? 

Thanks in advance,
Mangesh Edake. 

 
--- Daniel Jacobowitz <drow@false.org> wrote:

> On Sat, Nov 18, 2006 at 06:05:01AM -0800, Mangesh
> Edake wrote:
> > 
> > Hi,
> >    I looked for the patches provided by nathan. I
> > found those patches are for m68k and apply to the
> > files gdb/m68k-tdep.c and gdb/m68klinux-tdep.c
> 
> Those patches have nothing to do with this.
> 
> If you can't try CVS HEAD, see if it works, and tell
> us what
> happens if it doesn't work, then I'm sorry but we
> can't help
> you.
> 
> > There is no patch for ARM for gdb-6.x to make
> > gdbserver work on ARM platform. So we have decided
> to
> > continue with gdb-5.2.1 as it is patched. Now in
> this
> > case I have arm-elf-gdb version 6.4 and gdbserver
> that
> > will run on ARM board is from gdb-5.2.1, so will
> this 
> > create any problems due to version mismatch going
> > further?  
> 
> It should be fine.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery
> 



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com


      reply	other threads:[~2006-12-05 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17  8:53 Mangesh Edake
2006-11-17 14:18 ` Daniel Jacobowitz
     [not found]   ` <20061117142726.25304.qmail@web30605.mail.mud.yahoo.com>
2006-11-17 17:33     ` Daniel Jacobowitz
2006-11-18 14:05       ` Mangesh Edake
2006-11-18 16:31         ` Daniel Jacobowitz
2006-12-05 12:01           ` Mangesh Edake [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061205120058.3723.qmail@web50502.mail.yahoo.com \
    --to=m_edake@yahoo.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=kaushikkarandikar@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox