public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Heik H. Hellmich" <hellmich@mikro.ee.tu-berlin.de>
To: insight@sources.redhat.com
Subject: step through code
Date: Wed, 25 Sep 2002 03:58:00 -0000	[thread overview]
Message-ID: <3D9196F3.50E0A9F0@mikro.ee.tu-berlin.de> (raw)

Hi all,

I am using Insight GNU gdb 5.1 (--host=sparc-sun-solaris2.6
--target=powerpc-eabi) and have the problem that I cannot step through
the generated elf-code because the step/next/finish/continue buttons are
always greyed out for target=sim. I am able to load the elf-file and can
see the c-file and the corresponding asm-file in Insight's source
window.
The 2 commands how I created the elf-file are the following:

powerpc-eabi-gcc -Wall -gdwarf -msdata=eabi -mcpu=403 \
-I/work/hellmich/sftwr/libs/bsp/include \
-DV2PDK -DDEBUG -o ppc.o -c ppc.c

powerpc-eabi-gcc -Wall -gdwarf -msdata=eabi -mcpu=403 \
-I/work/hellmich/sftwr/libs/bsp/include \
-DV2PDK -DDEBUG -Wl,-T,/work/hellmich/sftwr/mapfiles/mapfile_ppc \
-u _boot -o ppc.elf ppc.o \
/work/hellmich/sftwr/libs/bsp/v2pdk/debug/bsp.a

bsp stands for board support packages and contains several c- and
asm-files (bootloader, controlling peripheral devices like UART, ...).

I would really appreciate a hint how I can solve this problem!

- Heik -

             reply	other threads:[~2002-09-25 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25  3:58 Heik H. Hellmich [this message]
2002-09-25  8:34 ` Keith Seitz
     [not found] <3D9323DB.C90B70D3@mikro.ee.tu-berlin.de>
2002-09-26  8:49 ` Keith Seitz
     [not found] <3D948874.99C32AFE@mikro.ee.tu-berlin.de>
2002-09-27  9:56 ` Keith Seitz
     [not found] <3D9491C7.84727946@mikro.ee.tu-berlin.de>
2002-09-27 10:18 ` Keith Seitz

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=3D9196F3.50E0A9F0@mikro.ee.tu-berlin.de \
    --to=hellmich@mikro.ee.tu-berlin.de \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).