|
From: Ben G. <gr...@ca...> - 2010-07-31 00:02:17
|
Hello! I am trying to use fork/execve to launch other programs running under valgrind from the parent. I'm seeing this in my logs. I know the comment talks about exe with very large text, but does the ~2MB shown in this printout mean it's not too large and maybe there is some other reason? Is it somehow invalid to run valgrind through fork/execve? Other apps seem to work fine under valgrind on this system, and I tried both the standard version that comes with Fedora 11 as well as today's SVN checkout. valgrind: mmap(0x38000000, 2080768) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments. valgrind: mmap(0x38000000, 2080768) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments. valgrind: mmap(0x38000000, 2080768) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments. My OS is 64-bit Fedora 11, 12GB RAM, core-i7 processor, etc. I tried under the 2.6.31 kernel as well as .34. My kernels are hand built and contain some hacks and patches, but hopefully nothing that could influence this. Thanks, Ben -- Ben Greear <gr...@ca...> Candela Technologies Inc http://www.candelatech.com |
|
From: Ben G. <gr...@ca...> - 2010-07-31 14:03:02
|
On 07/30/2010 04:26 PM, Ben Greear wrote: > Hello! > > I am trying to use fork/execve to launch other programs running under > valgrind from the parent. > > I'm seeing this in my logs. I know the comment talks about exe with very > large text, but does the ~2MB shown in this printout mean it's > not too large and maybe there is some other reason? > > Is it somehow invalid to run valgrind through fork/execve? I figured this out: I was running the parent process with --trace-children, and also explicitly running the children under valgrind. Looks like that is a bad idea. If someone wanted to update the UME error message to warn about that case that would be nice as well. Thanks, Ben > > Other apps seem to work fine under valgrind on this system, and > I tried both the standard version that comes with Fedora 11 as well as > today's SVN checkout. > > valgrind: mmap(0x38000000, 2080768) failed in UME with error 22 (Invalid argument). > valgrind: this can be caused by executables with very large text, data or bss segments. > valgrind: mmap(0x38000000, 2080768) failed in UME with error 22 (Invalid argument). > valgrind: this can be caused by executables with very large text, data or bss segments. > valgrind: mmap(0x38000000, 2080768) failed in UME with error 22 (Invalid argument). > valgrind: this can be caused by executables with very large text, data or bss segments. > > > My OS is 64-bit Fedora 11, 12GB RAM, core-i7 processor, etc. I tried under the 2.6.31 > kernel as well as .34. My kernels are hand built and contain some hacks and patches, > but hopefully nothing that could influence this. > > > Thanks, > Ben > -- Ben Greear <gr...@ca...> Candela Technologies Inc http://www.candelatech.com |