All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher R. Johnson" <cjohnson@gcctech.com>
To: cjohnson@gcctech.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: gdb problems
Date: Tue, 27 Jan 2004 12:13:25 -0500	[thread overview]
Message-ID: <40169C35.5020602@gcctech.com> (raw)
In-Reply-To: 4016965F.5060706@gcctech.com


Ok, answering some of my own questions:

in host-side gdb, use the two commands:
set solib-absolute-prefix
set solib-search-path

I set the first to /dev/null and the second to the path where my
filesystem is constructed and its /lib directory (where all my shared
libs are on the host).

All the below error messages go away, but I am left with my original
problem.  I can set breakpoints but they don't work.  What am I missing?

Christopher R. Johnson wrote:

>
> Maybe not the right list for this, if you have a suggestion for
> somewhere better let me know...
>
> My new tool chain build is working well, except that debugging with
> gdb/gdbserver is somewhat broken.  I figured out that I needed thread_db
> and have that built in now and delivered to the target platform.
>
> Problem #1: When I start host side gdb, I get the message:
> warning: unable to find dynamic linker breakpoint function
> GDB will be unable to debug shared library initializers
> and track explicitly loaded dynamic code
>
> I don't need to debug initializers, so I set a breakpoint at main and
> continue.  Two error messages appear:
> Error while mapping shared library sections:
> /lib/ld.so.1: No such file or directory
> Error while mapping shared library symbols:
> /lib/ld.so.1: No such file or directory
>
> The program starts and breakpoint don't work.
>
> Problem #2:  (Maybe related?) on the target side gdbserver, after
> starting things with "c" on the host side, this message appears:
> gdb: error initializing thread_db library.
> gdb: error initializing thread_db library.
>
> Yes, twice.
>
> Why is the host side looking in /lib for target libraries?  Can I
> control that?  How?
>
> Why is gdbserver on the target having trouble?  I see I have correctly
> delivered the thread_db library in /lib on the target, so what gives?
>
> Any help or guidance would be greatly appreciated.  I build my toolchain
> with crosstools.
>
> --
> Christopher R. Johnson
>
>
>

--
Christopher R. Johnson
Principal Software Engineer
GCC Printers
(781)276-8763


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-01-27 17:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 16:48 gdb problems Christopher R. Johnson
2004-01-27 17:13 ` Christopher R. Johnson [this message]
2004-01-27 17:13 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2013-04-08 11:03 GDB problems Gary Thomas
2013-04-08 12:30 ` Gary Thomas
2013-04-08 12:47   ` Paul Eggleton
2013-04-08 13:01     ` Gary Thomas
2013-04-08 17:34     ` Khem Raj
     [not found] <000701c0d99b$357cbf20$3196143e@jocke>
2001-05-10 22:09 ` gdb problems Wolfgang Denk
2001-05-11 10:25   ` Joakim Tjernlund
2001-05-10 17:19 Joakim Tjernlund
2001-05-10 17:40 ` Wolfgang Denk
2001-05-10 18:22 ` Scott Anderson
2001-05-11 10:23   ` Joakim Tjernlund
2001-05-11 15:38     ` Joakim Tjernlund

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=40169C35.5020602@gcctech.com \
    --to=cjohnson@gcctech.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.