From: Vermeulen Jan <Jan.Vermeulen@siemens.com>
To: 'Peter Barada' <pbarada@mail.wm.sps.mot.com>
Cc: peter@baradas.org, gdb@sources.redhat.com, Peter.Barada@motorola.com
Subject: RE: How to build application to run under the ppc simulator?
Date: Thu, 10 Apr 2003 06:02:00 -0000 [thread overview]
Message-ID: <57FD2C3A246F76438CA6FDAD8FE9F19597E9D6@hrtades7.atea.be> (raw)
Peter,
> >> and it bombs with:
> >>
> >> >Program terminated with signal SIGSEGV, Segmentation fault.
> >> >The program no longer exists.
> >> >[Switching to process 0]
> >> >(gdb)
> >
> >This is quite normal, because your program is executed correctly and
> >executes an 'blr' instruction at the end of the main
> routine. This makes the
> >simulated CPU jump to what's currently in the link register,
> which can be
> >anything. There it will do crazy things untill it finally
> segfaults :)
> >
> >If in doubt, just 'stepi' the program, watching the assembly
> be executed.
>
> I can't stepi from the start, I have to run it. How(actually,
> *where*) can I set a breakpoint at the *first* instruction so I can
> *then* stepi?
If your only function is 'foo', why not try "break foo" at the gdb command?
I just tried it out (same example as you) and it works. I can stepi in the
program and see that it jumps to 0x0 after the 'blr' instruction at the end
of 'foo' where it segfaults.
HTH,
Jan
next reply other threads:[~2003-04-10 6:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 6:02 Vermeulen Jan [this message]
2003-04-10 6:08 ` Peter Barada
-- strict thread matches above, loose matches on Subject: below --
2003-04-10 7:12 Vermeulen Jan
2003-04-09 6:33 Vermeulen Jan
2003-04-09 6:21 Vermeulen Jan
2003-04-09 16:14 ` Peter Barada
2003-04-09 4:40 Peter Barada
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=57FD2C3A246F76438CA6FDAD8FE9F19597E9D6@hrtades7.atea.be \
--to=jan.vermeulen@siemens.com \
--cc=Peter.Barada@motorola.com \
--cc=gdb@sources.redhat.com \
--cc=pbarada@mail.wm.sps.mot.com \
--cc=peter@baradas.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