Innards of LoadRunner - the compilation process
Submitted by Suresh Nageswaran on Mon, 17/01/2005 - 12:20.
Mercury LoadRunner | performance testing
Compilers and interpreters have always interested me. I can't remember when or how I started tinkering with Mercury LoadRunner's implementation. It seems clear that it compiler ANSI C - the actual stuff behind remained hidden and undocumented. In fact, it still is.
MI is a company run by rather smart people. Well, they wouldn't be worth close to a billion dollars if they hadn't! They took two disparate opensource tools and stuck them together and created an interpreter interface as a front end. The tools I'm talking about are:
* The GNU C Pre-Processor
* The LCC Retargetable C Compiler
The tools I used to acquire this re-engineered understanding are rather simple - Dependency Walker (www.dependencywalker.com) and TextPad (for parsing reg-exps on Win32 platforms). I will blogging about my journeys through the bin folders shortly.
MI is a company run by rather smart people. Well, they wouldn't be worth close to a billion dollars if they hadn't! They took two disparate opensource tools and stuck them together and created an interpreter interface as a front end. The tools I'm talking about are:
* The GNU C Pre-Processor
* The LCC Retargetable C Compiler
The tools I used to acquire this re-engineered understanding are rather simple - Dependency Walker (www.dependencywalker.com) and TextPad (for parsing reg-exps on Win32 platforms). I will blogging about my journeys through the bin folders shortly.