From: Claudio Fontana <claudio.fontana@gmail.com>
To: lynx.abraxas@freenet.de
Cc: linux-assembly@vger.kernel.org
Subject: Re: precise debugging of inline asm
Date: Sun, 01 Jun 2008 19:27:26 +0200 [thread overview]
Message-ID: <4842DBFE.4080404@gmail.com> (raw)
In-Reply-To: <20080601150140.GA2832@drago>
lynx.abraxas@freenet.de wrote:
> Hello!
>
>
> The mentioning of gdb in this mailinglist gave me the idea to ask my
> unresolved question here as well:
>
> Trying to port cpt2 to linux I have an inline assembly part of about 100 lines
> that causes a segmentation fault while juggling around with memory. When I use
> gdb for debugging it sadly only points me to the line where the inline asm
> starts. I haven't been able to figure out how to get a more precise info in
> what line the actual segmentation fault comes from.
> Does anybody here know if that is at all possible and if so, how? Would labels
> to each line help?
>
> Thanks for any help or hints.
> Lynx
On x86, try for example
(gdb) disassemble $eip $eip+20
Also see
(gdb) info registers
Cld
next prev parent reply other threads:[~2008-06-01 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 15:01 precise debugging of inline asm lynx.abraxas
2008-06-01 17:27 ` Claudio Fontana [this message]
2008-06-08 12:36 ` lynx.abraxas
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=4842DBFE.4080404@gmail.com \
--to=claudio.fontana@gmail.com \
--cc=linux-assembly@vger.kernel.org \
--cc=lynx.abraxas@freenet.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.