public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: dharter@lycos.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is this a kernel problem? segmentation fault
Date: 14 Nov 2001 13:35:39 +0100	[thread overview]
Message-ID: <je8zd9o7hg.fsf@sykes.suse.de> (raw)
In-Reply-To: <IPKBFBEEDJJJACAA@mailcity.com>
In-Reply-To: <IPKBFBEEDJJJACAA@mailcity.com> ("Donald Harter"'s message of "Tue, 13 Nov 2001 19:40:08 -0600")

"Donald Harter" <dharter@lycos.com> writes:

|>      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?

Perhaps a stack overflow, or stack pointer is pointing to lala land.

Andreas.

-- 
Andreas Schwab                                  "And now for something
Andreas.Schwab@suse.de				completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5

      parent reply	other threads:[~2001-11-14 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14  1:40 Is this a kernel problem? segmentation fault Donald Harter
2001-11-14 10:37 ` Terje Eggestad
2001-11-14 12:01 ` Roman Zippel
2001-11-14 12:35 ` Andreas Schwab [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=je8zd9o7hg.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=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