|
From: <ud...@fa...> - 2003-12-11 01:26:52
|
Hi All, I am a newbie to valgrind. So I was wondering if anybody could help me with this. When I run my program through valgrind valgrind <prg name> It runs fine with out any seg faults.Valgrind does complain about some Conditional jump or move depends on uninitialised value(s) But this seems to be library related and not my program. But when I run it outside of valgrind, my program seg faults I have spent 8 hours trying to solve this. I cant get gdb to look at it because it says it cant find the source. WHat should I do? Thank you for your suggestions. |
|
From: Jeremy F. <je...@go...> - 2003-12-11 02:13:05
|
On Wed, 2003-12-10 at 17:26, ud...@fa... wrote: > Hi All, > I am a newbie to valgrind. So I was wondering if > anybody could help me with this. > > When I run my program through valgrind > > valgrind <prg name> > > It runs fine with out any seg faults.Valgrind does > complain about some > > Conditional jump or move depends on uninitialised > value(s) > > But this seems to be library related and not my > program. > > > But when I run it outside of valgrind, my program seg > faults > > I have spent 8 hours trying to solve this. I cant get > gdb to look at it because it says it cant find the > source. > > WHat should I do? A good start would be to post a lot more detail. How about posting the actual output of Valgrind? Just because the error is reported when library code is running, it doesn't mean the bug is in the library. If you give the library bad values, then Valgrind will see a problem with what the library's doing, but it is your bug. Why won't gdb help? If you run "gdb your_program" and it stops with a SEGV, then you can get lots of information out of gdb, even without source. Like: who called the faulting code, what's the faulting address, etc. J |