|
From: B.Senthilkumar <bse...@ad...> - 2005-08-15 09:33:09
|
Hi Tom,
Thanks for your response.
I am trying to find two modules in valgrind source code
1. How valgrind handle code for convertion machine code -> u code
That's I got answer from your mail " The translation starts
with m_translate.c which then uses the code in the VEX library to do the
translation.".From that i understood the translation part is not handle
in open source code right , it handled by VEX library.
2. How valgrind creates a virtual process to run the client program.
Could you please help me where to start and specify the
function name.
Thanks,
Senthilkumar.
Tom Hughes wrote:
>In message <430...@ad...>
> B. Senthilkumar <bse...@ad...> wrote:
>
>
>
>>I want to know how to convert ELF machine code to U->code.. where the
>>code handle in valgrind source code and same could you please point
>>out how to read ELF file format.
>>
>>
>
>There isn't really any such thing as 'ELF machine code'. ELF is a file
>format and some sections of an ELF file will contain machine code. If
>you want to know about ELF then I'd start with the ELF standard:
>
> http://x86.ddj.com/ftp/manuals/tools/elf.pdf
>
>The wikipedia article on ELF has a number of other links to useful
>information:
>
> http://en.wikipedia.org/wiki/Executable_and_Linkable_Format
>
>Most of the time valgrind doesn't have to worry about ELF at all. The
>code that does is the initial loader (in m_ume.c) and the code that
>finds the symbol tables and debugging information (in the m_debuginfo
>directory).
>
>UCode is no longer used by valgrind in version 3 so you probably don't
>want to worry about that - the VEX engine is now used to handle the
>disassembly/instrumentation/reassembly of code.
>
>The translation starts with m_translate.c which then uses the code in
>the VEX library to do the translation.
>
>Tom
>
>
>
--
http://www.finepick.com FREE- Simple for Buy/sell!
|