Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Julien <jducourt@noos.fr>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: Specifying a device tree for psim within gdb
Date: Sun, 14 Oct 2001 12:22:00 -0000	[thread overview]
Message-ID: <1003087847.1316.82.camel@athlon_force.localdomain> (raw)
In-Reply-To: <3BC9D2F1.10409@cygnus.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

le dim 14-10-2001 at 20:01 Andrew Cagney a écrit :
> > Hi,
> > 
> > I'm using gdb 5.0 on a linux x86 box, configured with
> > --target=powerpc-unknown-eabi. I want to debug a raw memory image (my
> > exec+some data) using the psim simulator.
> > 
> >  When I run the simulator directly (powerpc-unknown-eabi-run), I specify
> > a device-tree (whith a 'file' device to load my image). 
> > But when I use the debugger I don't know how to specify a device-tree.
> > The psim doc in sources.redhat.com talks about an attach patch but all
> > the links seem to be broken. 
> > Does someone have this patch ? Or is there another way to specify the
> > device tree within gdb ?
> 
> try:
> 	(gdb) target sim <same-options>
> 
> Andrew
> 
> 
> 
Thanks all, my image runs now within gdb.
gdb didn't want to start or load at first since I was only giving it a
symbol-file (and no exec) since my device tree was :
/openprom/init/file
/openprom/init/file/file-name psim.boot  # raw image with exec in it
/openprom/init/file/real-address 0x4000
/openprom/init/register/pc 0x4000

So I put a fake exec (loaded at a higher address) with just 
	.text
_start:
	ba 0x4000

and gave it as the program to debug for gdb and it ran fine.

Julien.


-- 

Julien Ducourthial (jducourt@noos.fr)


  reply	other threads:[~2001-10-14 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14 10:54 Julien
2001-10-14 11:01 ` Andrew Cagney
2001-10-14 12:22   ` Julien [this message]
2001-10-14 11:13 ` Mark Peek

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=1003087847.1316.82.camel@athlon_force.localdomain \
    --to=jducourt@noos.fr \
    --cc=ac131313@cygnus.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