From: Thiago Silva <thiago.silva@kdemail.net>
To: linux-assembly@vger.kernel.org
Subject: Re: nasm / code distance
Date: Sat, 08 Apr 2006 11:09:52 +0000 [thread overview]
Message-ID: <200604081109.52115.thiago.silva@kdemail.net> (raw)
In-Reply-To: <20060408094752.GA5931@wintermute>
Well...the code is really a big one.
To clarify, I made simple test:
On the entry point, I read some data in the .data section (such as "mov eax,
dword [_r]"). Running valgrind, this read is not shown on the error
reporting.
Then, I copied this same read code and pasted it on a function in the end of
the file (is a pretty big source file). Then, valgrind complained that this
was an invalid read!!
So I though there might be something I'm missing...
The same goes for the jmp instructions getting the "short jump out of range".
On Saturday 08 April 2006 09:47, you wrote:
> On Fri, Apr 07, 2006 at 06:47:32PM +0000, Thiago Silva wrote:
> > Hello, I'm having some troubles with an asm application.
>
> It's hard to say anything specific without you showing the problematic
> parts of your code.
>
> Leslie
--
+Thiago Silva
next prev parent reply other threads:[~2006-04-08 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 18:47 nasm / code distance Thiago Silva
2006-04-08 9:47 ` leslie.polzer
2006-04-08 11:09 ` Thiago Silva [this message]
2006-04-08 14:55 ` Frank Kotler
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=200604081109.52115.thiago.silva@kdemail.net \
--to=thiago.silva@kdemail.net \
--cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).