|
From: Edward M. <em...@li...> - 2008-06-21 04:30:18
|
I read that there was a patch available last year which would provide the stack information for sill arg warnings. I have a malloc call with a negative value that I really would like to track down. I am running valgrind 3.3.0 and valgrind 3.2.1. Any help or suggestions would be great, Ed |
|
From: Christopher L. <cl...@an...> - 2008-06-21 11:26:33
|
On Fri, Jun 20, 2008 at 04:12:30PM -0700, Edward Maros wrote: > I read that there was a patch available last year which would provide > the stack information for sill arg warnings. I have a malloc call with a > negative value that I really would like to track down. I am running > valgrind 3.3.0 and valgrind 3.2.1. > > Any help or suggestions would be great, > Ed Also, if you cannot track this down and have debugging symbols enabled for your libc, you can always set a conditional breakpoint to find the culprit - or just wrap malloc in a macro as well. -cl |
|
From: Edward M. <em...@li...> - 2008-06-22 05:06:04
|
Christopher Layne wrote: > On Fri, Jun 20, 2008 at 04:12:30PM -0700, Edward Maros wrote: > >> I read that there was a patch available last year which would provide >> the stack information for sill arg warnings. I have a malloc call with a >> negative value that I really would like to track down. I am running >> valgrind 3.3.0 and valgrind 3.2.1. >> >> Any help or suggestions would be great, >> Ed >> > > Also, if you cannot track this down and have debugging symbols enabled > for your libc, you can always set a conditional breakpoint to find the > culprit - or just wrap malloc in a macro as well. > > -cl > The challenge that I have is that my program is mostly c++ so I am not sure who is doing the malloc. Can you give me a slightly more detailed description on how to track down this type of error? Thanks, Ed |