valgrind segmentation faults every time

Thompson Harmon [US], Stanley W. Stanley.Harmon at sperry.ngc.com
Thu Jun 15 21:00:55 UTC 2006


 

> -----Original Message-----
> From: busybox-bounces at busybox.net 
> [mailto:busybox-bounces at busybox.net] On Behalf Of Rob Landley
> Sent: Thursday, June 15, 2006 3:19 PM
> To: busybox at busybox.net
> Cc: Thompson Harmon [US], Stanley W.
> Subject: Re: valgrind segmentation faults every time
> 
> On Wednesday 14 June 2006 8:31 pm, Thompson Harmon [US], 
> Stanley W. wrote:
> > All,
> >
> >    I built an embedded system using buildroot (from 20050924), gcc
> > (v4.0.0),  uClibc (v0.9.28 snapshot - from Aug - Sept 2005), busybox
> > (v1.1.0-pre1 snapshot - from Aug - Sept 2005), binutils (v2.16.1),
> > valgrind (v2.4.0), etc...  Every time I run valgrind (e.g.: valgrind
> > --tool=callgrind ../my_app) the only output I get is "Segmentation
> > fault".  I also tried to use the valgrind from Fedora Core 4 - same
> > result.  Even valgrind --help and valgrind by itself 
> produces the same
> > result.  Any help would be greatly appreciated.
> 
> From that information, I have no idea even where to start.  
> Have you ever 
> gotten valgrind to work before?  Is it valgrind segfaulting, 
> or the system 
> running under valgrind?  Does the app fail if you _don't_ use 
> Valgrind?  (In 
> which case, poke the valgrind developers.)  What the heck is 
> ../your_app?  
> (BusyBox?)  The buildroot mailing list is uclibc at uclibc.org, not here.
> 
> (I'd also point out that you never mentioned which config 
> you're using for 
> uClibc or BusyBox, but I'm not going to rebuild either to try 
> to reproduce 
> this right now.  Obviously, this works for other people...)
> 
> > Thanks,
> > Stan
> 
> Rob
> -- 
> Never bet against the cheap plastic solution.
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
> 

Rob,

   No, Valgrind never worked my system.  Valgrind is the item which is
segfaulting.  My system and my app (a control system) both run without
fail on their own.  In fact, my system with my app has run continuously
for 3 weeks.  I am trying to use Valgrind to profile my app in hopes of
determining which subprogram is using up my cpu time.  As for the
mailing list, you are correct.  I should have posted this to the
buildroot mailing list.  So, I will post this response to their as well
in case it is a buildroot config issue.  My next post will be to the
Valgrind developers.

Thanks for the info,
Stan




More information about the uClibc mailing list