Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Magdalena.Iovescu@mail.uh.edu
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Remote debuggind with gdb 5.3
Date: Fri, 25 Apr 2003 15:50:00 -0000	[thread overview]
Message-ID: <482063800.1051285844584.JavaMail.root@localhost> (raw)

How do I make sure of that? Just by building my own filesystem? 

I tried to copy the library files fom my host to the target file system, and the system crashes. When I try to bring it up again, I get this:

     VFS: Mounted root (nfs filesystem).
     Freeing init memory: 76K
     init: error while loading shared libraries: cannot open shared 
     object file: cannot load shared object file: No such file or directory
     Kernel panic: Attempted to kill init!

Regards,

Magdalena

>Depends on how you work.  I recommend using the exact same headers and
>libraries on host and target; otherwise really strange things can
>happen.
>
>On Thu, Apr 24, 2003 at 03:17:00PM -0500, Magdalena.Iovescu@mail.uh.edu wrote:
>> Thanks for answering.
>> I'm using an ARM filesystem from Wearable group, and that doesn't have this file anywhere. I have them though on my host, in my toolchain directory (/opt/arm-linux/arm-linux/lib). I tried copying it to the /lib on my target, but then there were other files missing. 
>> 
>> Is there a nicer way to get these files on the target filesystem?
>> 
>> Sorry for the basic questions, I'm new at embedded Linux.
>> 
>> Thanks,
>> 
>> Magdalena
>> 
>> >On Thu, Apr 24, 2003 at 02:16:24PM -0500, Magdalena.Iovescu@mail.uh.edu wrote:
>> >> Hello.
>> >> 
>> >> I am trying to setup remote debugging on an ARM platform. I compiled and
>> >> installed gdb 5.3 on host and target side (following 'the recipe' on
>> >> www.kegel.com/linux/gdbserver.html). I even applied the --with-solib-absolute-prefix patch, and I still got this error after that:
>> >> 
>> >> When I try to start the server on the target, I get this:
>> >> 
>> >> [guest@MyHost guest]$gdbserver host:3000 hello
>> >> gdbserver: error in loading shared libraries: libthread_db.so.1: cannot open
>> >> shared object file: No such file or directory
>> >> 
>> >> Any suggestions on how to solve this would be greatly appreciated.
>> >
>> >Exactly what the error message says: find libthread_db.so.1 on your
>> >target.  You must have an ARM version on your host somewhere if you
>> >were able to build thread support.
>> >
>> >-- 
>> >Daniel Jacobowitz
>> >MontaVista Software                         Debian GNU/Linux Developer
>> >
>> 
>
>-- 
>Daniel Jacobowitz
>MontaVista Software                         Debian GNU/Linux Developer
>


             reply	other threads:[~2003-04-25 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 15:50 Magdalena.Iovescu [this message]
2003-04-25 15:55 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24 20:17 Magdalena.Iovescu
2003-04-24 20:19 ` Daniel Jacobowitz
2003-04-24 19:16 Magdalena.Iovescu
2003-04-24 19:21 ` Daniel Jacobowitz

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=482063800.1051285844584.JavaMail.root@localhost \
    --to=magdalena.iovescu@mail.uh.edu \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.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