linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brendan J Simon <Brendan.Simon@ctam.com.au>
To: linux-embedded <linux-embedded@waste.org>,
	Cross-GCC <crossgcc@sourceware.cygnus.com>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: cross-compiling & debugging embedded-linux apps
Date: Fri, 31 Dec 1999 15:50:29 +1100	[thread overview]
Message-ID: <386C3615.E14AE6DD@ctam.com.au> (raw)



I have a powerpc embedded system (MPC860, 4MB Flash, 16MB RAM, ethernet,
rs232).  I have compiled the kernel and can boot it using a root
filesystem via initrd or nfs.  The root filesystem is a minimal one that
was on the linuxppc-embedded ftp site.  It basically has /bin/sh,
/bin/ls and a few libraries in /lib.

I NEED to be able to compile apps from the sources.  I have managed to
cross-compile ncurses and bash.  I can't get bash to run at all (even a
statically compiled version).  I get segmentaion faults.  I'm currently
using SASH which I have cross-compiled as a static binary.  I compiled a
test app (bjs1.c) which outputs a string every second.  It is compiled
as a static binary (bjs1-static) and a shared binary (bjs1-shared).  The
static binary works but the shared one does not.  I assume it is some
library problem but I can't figure out what.  The output of the sash
session is below.

Stand-alone shell (version 1.0)
> ./bjs1-static
BJS1: Brendan was here
BJS1: Brendan was here
BJS1: Brendan was here
pid 7: killed (signal 2)
>
> ./bjs1-shared
pid 8: killed (signal 11)
>

I have all the libraries on the root filesystem.  The rpc.nfsd daemon
seems to read the entire file but sash says the process is killed with
signal 11 (segmentation fault).  I have no idea how to debug this.  I
don't think there is a simulator for the mpc860 as part of gdb.  Is
there a way of debugging this on the target with powerpc-gdb and an
ethernet or serial connection ?

How does the kernel know where to look for libraries ?  I assume there
are some default locations like /lib.  I haven't got an ld.so.conf setup
nor do I have ldconfig.

It can't be that hard to get a simple 10 line program to execute as a
shared binary.  It must be something really simple that I am missing.

Thanks for any help,
Brendan Simon.


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

             reply	other threads:[~1999-12-31  4:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-31  4:50 Brendan J Simon [this message]
1999-12-31  6:58 ` cross-compiling & debugging embedded-linux apps Alan Mimms
1999-12-31 16:07   ` Jim Lewis
2000-01-04  0:30     ` Brendan J Simon
2000-01-04  3:16       ` Alan Mimms
1999-12-31 16:28 ` Jim Lewis
2000-01-01  5:59   ` Jeff Millar
2000-01-01 22:17   ` Alan Mimms
2000-01-03 12:23 ` Kai Ruottu
     [not found]   ` <3871A78E.F18B0161@ctam.com.au>
2000-01-04 20:07     ` Kai Ruottu
2000-01-14  9:27       ` dony

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=386C3615.E14AE6DD@ctam.com.au \
    --to=brendan.simon@ctam.com.au \
    --cc=crossgcc@sourceware.cygnus.com \
    --cc=linux-embedded@waste.org \
    --cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).