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 - : send the line "unsubscribe linux-assembly" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
- References:
- nasm / code distance
- From: Thiago Silva
- Re: nasm / code distance
- From: leslie . polzer
- nasm / code distance
- Prev by Date: Re: nasm / code distance
- Next by Date: please help me
- Previous by thread: Re: nasm / code distance
- Next by thread: Re: nasm / code distance
- Index(es):