On Mon, Jun 21, 2010 at 8:03 AM, Pramod <[email protected]> wrote: >> >> On Fri, Jun 18, 2010 at 1:18 PM, Pramod <akpramod <at> gmail.com> wrote: >> > >> > I have cross-compiled valgrind 3.5.0 to work on MontaVista Linux. >> > >> > After installing (copied bin, lib, > include directories to montavista machine), > >> > and running valgrind with no arguments, > I get a core file from memcheck. >> > >> > Using GDB, I see that the core occurs at line 251 in mc_leakcheck.c. >> > > Thanks Bart for the reply. > As mentioned in my original post: > I have not provided any input arguments to > valgrind when it dumped core. > > Also, I cross-compiled valgrind on host Solaris > for MontaVista Linux target.
The fact that Valgrind has been cross-compiled shouldn't affect its behavior. Sorry, I had overlooked that no input arguments were provided. You can see what happens while Valgrind starts by running the following command: valgrind -v -d -d Bart. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
