From: "Donald Harter" <dharter@lycos.com>
To: linux-kernel@vger.kernel.org
Subject: Is this a kernel problem? segmentation fault
Date: Tue, 13 Nov 2001 19:40:08 -0600 [thread overview]
Message-ID: <IPKBFBEEDJJJACAA@mailcity.com> (raw)
I started by debugging this program where I was getting a segmentation fault. I used gdb and traced the bug to a call instruction. I dissasembled the code and stepped through the instructions. The program got a segmentation fault when it executed an assembly language call instruction. Using gdb I was able to disassemble the instructions at the called address. Why can gdb disasemble instructions at a call address and a call to that address fails with a segmentation fault? Is this a kernel problem? I am using kernel version 2.2.15. Any suggestions would be appreciated. I tried kernel 2.4.4 and the same thing happens. I have searched this mailing list archive and did find some posts about segmentation faults/ kernel bugs, but they did not resolve this problem. I use egcs 1.1-2 and ld 2.9.5 versions.
next reply other threads:[~2001-11-14 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 1:40 Donald Harter [this message]
2001-11-14 10:37 ` Is this a kernel problem? segmentation fault Terje Eggestad
2001-11-14 12:01 ` Roman Zippel
2001-11-14 12:35 ` Andreas Schwab
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=IPKBFBEEDJJJACAA@mailcity.com \
--to=dharter@lycos.com \
--cc=linux-kernel@vger.kernel.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