|
From: Panchabakesan T. <pan...@gm...> - 2011-08-22 20:28:54
|
Hi, I need to use the Valgrind tool for analysing an application which runs on IBM 4690 OS. Should the tool be built with the .x86 extention and then sent to my target machine for analyzing my application or should that be directly installed on my target machine? I have downloaded the latest Valgrind 3.6.1 and any help on this is highly appreciated... Thanks, Pancha |
|
From: Florian K. <br...@ac...> - 2011-08-23 17:34:18
|
On 08/22/2011 04:28 PM, Panchabakesan Thiagarajan wrote: > Hi, > > I need to use the Valgrind tool for analysing an application which runs on > IBM 4690 OS. > Should the tool be built with the .x86 extention and then sent to my target > machine for analyzing my application or should that be directly installed on > my target machine? > Neither will do you any good. IBM 4690 is not a supported platform. See here: http://valgrind.org/info/platforms.html Florian |
|
From: Panchabakesan T. <pan...@gm...> - 2011-08-24 21:12:37
|
Thanks for your reply... I'm a bit new to this developing environment, so took some time to analyse on whats happening. We develop on a Windows platform using Cygwin and the compiler is Intel ICC compiler. The executables are typically .386 or .286. The target machine runs on IBM 4690 OS, in its turn was a derivative of Concurrent DOS. Though the flavours are different the underlying OS remains the same and so as the memory management too right? so could this tool be used with minor modificaitons if required for adopting to this OS? On Tue, Aug 23, 2011 at 12:34 PM, Florian Krohm <br...@ac...> wrote: > On 08/22/2011 04:28 PM, Panchabakesan Thiagarajan wrote: > > Hi, > > > > I need to use the Valgrind tool for analysing an application which runs > on > > IBM 4690 OS. > > Should the tool be built with the .x86 extention and then sent to my > target > > machine for analyzing my application or should that be directly installed > on > > my target machine? > > > > Neither will do you any good. > IBM 4690 is not a supported platform. See here: > http://valgrind.org/info/platforms.html > > Florian > |
|
From: Florian K. <br...@ac...> - 2011-08-26 14:08:39
|
On 08/24/2011 05:12 PM, Panchabakesan Thiagarajan wrote: > Thanks for your reply... I'm a bit new to this developing environment, so > took some time to analyse on whats happening. > We develop on a Windows platform using Cygwin and the compiler is Intel ICC > compiler. The executables are typically .386 or .286. The target machine > runs on IBM 4690 OS, in its turn was a derivative of Concurrent DOS. > Though the flavours are different the underlying OS remains the same The underlying OS is Windows and that is not supported. > so could this tool be used with minor > modificaitons if required for adopting to this OS? > No, this would be a major undertaking. For one thing you would have to wrap all system calls and tell valgrind what they do to memory (read, write, allocate, etc). I doubt that there is sufficient information about Windows system calls available to make porting valgrind a well defined task. Florian |