From: norbert.c.esser@philips.com
To: <sid@sources.redhat.com>
Subject: Segmentation Fault sid&gdb
Date: Tue, 16 Jan 2001 01:23:00 -0000 [thread overview]
Message-ID: <0056890019074750000002L902*@MHS> (raw)
Hello,
I'm trying to use gdb in combination with sid.
I followed the example in the SID Faq-O-Matic on "how does one build and run sid".
I compiled the following program for the ARM
#include <stdio.h>
int main
{ printf("Hello world!\n");
return 0;
}
with arm-elf-gcc -mlittle-endian hello.c -o hello.x
And then started sid and gdb in the follwing way:
arm-elf-sid --gdb=2000 -EL &
arm-elf-gdb hello.x
I then gave the follwing gdb commands:
(gdb) target remote localhost:2000
(gdb) load
(gdb) break main
Up to here everything seems to work
But I now give the follwing command:
(gdb) cont
Then I get the following message:
Program received signal SIGSEGV, Segmentation fault
Which I think is probably due to the way gdb handles breakpoints (am I correct?).
But I I then want to step or continue the program in which way what so ever, I get the
message
Fault (memory, 0xfffffffc) pc=0x80e8
And then nothing happens anymore.
I would for example like to be able to set multiple breakpoints and if the program stops on a
breakpoint continue the program until it stops on another breakpoint.
Is this possible? If yes, what am I doing wrong?
Can anybody shed some light on this subject?
Thanks.
next reply other threads:[~2001-01-16 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 1:23 norbert.c.esser [this message]
2001-01-16 4:39 ` Frank Ch. Eigler
2001-01-16 6:38 norbert.c.esser
2001-01-16 9:55 ` Frank Ch. Eigler
2001-01-16 14:26 ` matthew green
2001-01-16 11:04 Bernard Dautrevaux
2001-01-16 13:09 ` Frank Ch. Eigler
2001-01-16 14:46 ` Ben Elliston
2001-01-17 0:37 Bernard Dautrevaux
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='0056890019074750000002L902*@MHS' \
--to=norbert.c.esser@philips.com \
--cc=sid@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).