|
From: Rohit <roh...@ng...> - 2009-02-23 22:48:30
|
Hi all, I have a problem running valgrind. I can comple and run it just fine on the development system, but not the target. When I try to run there, I get a floating point exception at startup when I try to run valgrind. Has anyone seen this before? If so, can you provide some insight into this? Kind regards. |
|
From: Bart V. A. <bar...@gm...> - 2009-02-24 06:57:18
|
On Mon, Feb 23, 2009 at 9:59 PM, Rohit <roh...@ng...> wrote: > I have a problem running valgrind. I can comple and run it just fine on the > development system, but not the target. When I try to run there, I get a > floating point exception at startup when I try to run valgrind. Has anyone seen > this before? If so, can you provide some insight into this? Which Valgrind version are you using, and what is the CPU architecture of the target ? Bart. |
|
From: Rohit <Roh...@ng...> - 2009-02-24 16:11:03
|
Bart Van Assche <bart.vanassche <at> gmail.com> writes: > > On Mon, Feb 23, 2009 at 9:59 PM, Rohit <rohit.tanneeru <at> ngc.com> wrote: > > I have a problem running valgrind. I can comple and run it just fine on the > > development system, but not the target. When I try to run there, I get a > > floating point exception at startup when I try to run valgrind. Has anyone seen > > this before? If so, can you provide some insight into this? > > Which Valgrind version are you using, and what is the CPU architecture > of the target ? > > Bart. Dear Bart, Thank you for getting back to me. Here is the information that you requested. Valgrind version = 3.4.0 CPU architecture = Intel Pentium 4 Redhat 3.6 Best regards. |
|
From: Julian S. <js...@ac...> - 2009-02-24 16:24:27
|
> > > I have a problem running valgrind. I can comple and run it just fine on > > > the development system, but not the target. When I try to run there, I > > > get a floating point exception at startup when I try to run valgrind. This is on a 32-bit embedded ppc target, right? If yes, try the valgrind-3.4.1.SVN-9098-1883 snapshot available from http://www.valgrind.org/downloads/current.html. It contains a fix for that problem. J |