From: Frederic Kwiatkowski <stagedrt@gmail.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb@sourceware.org
Subject: Re: "SIGSEGV, Segmentation fault." message on a standard program
Date: Thu, 09 Feb 2006 09:36:00 -0000 [thread overview]
Message-ID: <5fb065d90602090136m68090bf0w@mail.gmail.com> (raw)
In-Reply-To: <8f2776cb0602090128m546c34a1tffd1c956e029007b@mail.gmail.com>
If i run the program on the arm-linux system, everything goes right,
that's why i don't understand the reason of the segmentation fault:
# /mnt/nfs/frk/essai_gdb/essai_gdb
Enter first number : 1
Enter second number : 2
The sum is : 3
#
2006/2/9, Jim Blandy <jimb@red-bean.com>:
> On 2/9/06, Frederic Kwiatkowski <stagedrt@gmail.com> wrote:
> > 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.
>
> What happens when you run your program on the arm-linux system,
> without gdbserver?
>
prev parent reply other threads:[~2006-02-09 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 8:36 Frederic Kwiatkowski
2006-02-09 9:28 ` Jim Blandy
2006-02-09 9:36 ` Frederic Kwiatkowski [this message]
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=5fb065d90602090136m68090bf0w@mail.gmail.com \
--to=stagedrt@gmail.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.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