From: Frederic Kwiatkowski <stagedrt@gmail.com>
To: gdb@sourceware.org
Subject: "SIGSEGV, Segmentation fault." message on a standard program
Date: Thu, 09 Feb 2006 08:36:00 -0000 [thread overview]
Message-ID: <5fb065d90602090036x63e59e75t@mail.gmail.com> (raw)
Hello all
I'm actually trying to debug a basic application to a remote host.
So i've crosscompiled my application, launch gdbserver 6.4 on my
remote host and gdbtui 6.4 or gdb 6.4on my local host
So i can see the code source of the application and place break point
but if i try to use the "continue" function, the system send me the
following message:
>(>gdb) continue
>>Continuing.
>>
>>Program received signal SIGSEGV, Segmentation fault.
>>0x4000e54c in ?? ()
Next, if i retry to launch the continue function, i've got the following:
>>(gdb) continue
>vContinuing.
>>
>>Program terminated with signal SIGSEGV, Segmentation fault.
>>The program no longer exists.
and the server is exited:
>>Listening on port 2345
>>Remote debugging from host 192.168.0.250
>>
>>Child terminated with signal = b
>>
>>Child terminated with signal = 0xb
>>GDBserver exiting
So i've tried to debug the application on my desktop computer, with no
remote (gdbserver and gdb hosted on the desktop), and then, everything
is right.
I've compiled gdbserver and the application with arm-linux-gcc 3.4.4
and compiled gdb and gdbtui with the arm-linux target option
Does any body have an idea about it?
With kind of regards
Frederic Kwiatkowski
next reply other threads:[~2006-02-09 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 8:36 Frederic Kwiatkowski [this message]
2006-02-09 9:28 ` Jim Blandy
2006-02-09 9:36 ` Frederic Kwiatkowski
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=5fb065d90602090036x63e59e75t@mail.gmail.com \
--to=stagedrt@gmail.com \
--cc=gdb@sourceware.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