valgrind

问题 I need to read a file and store the data from the file into a structure. The first line of the file contains the size of the array of structs that i have to dynamically allocate. 4 12/04/2010 Interview went well I think, though was told to wear shoes. 18/04/2010 Doc advised me to concentrate on something... I forget. 03/05/2010 Was asked today if I was an art exhibit. 19/05/2010 Apparently mudcakes not made of mud, or angry wasps. I am to run my code perfectly in Windows but when I run in

问题 I'm trying to understand the output from valgrind having executed it as follows: valgrind --leak-check=yes "someprogram" The output is here: ==30347== ==30347== HEAP SUMMARY: ==30347== in use at exit: 126,188 bytes in 2,777 blocks ==30347== total heap usage: 4,562 allocs, 1,785 frees, 974,922 bytes allocated ==30347== ==30347== LEAK SUMMARY: ==30347== definitely lost: 0 bytes in 0 blocks ==30347== indirectly lost: 0 bytes in 0 blocks ==30347== possibly lost: 0 bytes in 0 blocks ==30347==

问题 I want to use valrgind at a specific time while my program is running. For example, when I use -O3 it will take 0.5 hours to reach the desired point. When I use -g -ggdb it will take nearly 2.5 hours to reach the desired point. Now if I use valgrind with -g -ggdb , the program is extremely slow and I can not predict when it reach the desired point. What should I do? 来源： https://stackoverflow.com/questions/18438963/using-valgrind-at-specific-point-while-running-program

问题 I'm implementing a hashtable that has a remove_entry function as well as a clear_table function. Right now I'm getting memory read errors pertaining to the remove_entry function. And help would be greatly appreciated These are my structures: typedef struct bucket { char *key; void *value; struct bucket *next; } Bucket; typedef struct { int key_count; int table_size; void (*free_value)(void *); Bucket **buckets; } Table; Here's my function: int remove_entry(Table * table, const char *key){

问题 I'm quite new in using valgrind. I'm running tests for my C library. I've tryed to run it under valgrind and got some very valuable info about possible errors in my code. One thing that bothers me is beginning of every valgrind session is full of messages like this: DWARF2 CFI reader: unhandled CFI instruction 0:22 IIUC it's unrelated to problems in my code and I'd like to disable them to simplify analysis of other errors. I've read valgrind help but can't find the proper command-line option.

问题 The following code: #include <stdlib.h> #include <string.h> int main() { char *s = strdup("keep-alive"); if(strcasestr(s, "close")) { } free(s); return 0; } gives the following error in Valgrind: ==13183== Invalid read of size 8 ==13183== at 0x4F53F94: __strcasestr_sse42 (emmintrin.h:685) ==13183== by 0x4005BF: main (in /home/aaron/dev/strtest) ==13183== Address 0x51ce048 is 8 bytes inside a block of size 11 alloc'd ==13183== at 0x4C28F9F: malloc (vg_replace_malloc.c:236) ==13183== by

问题 So given this output: ==80518== Invalid read of size 4 ==80518== at 0x558D: Node::ReadFolder(GFile*) (in ./ScribeRecoverMail2) ==80518== by 0x7B61: Worker::Export(GFile*, GArray<Node*>&) (in ./ScribeRecoverMail2) ==80518== by 0x8F7A: Worker::Main() (in ./ScribeRecoverMail2) ==80518== by 0x142D64: ThreadEntryPoint(void*) (in /Users/matthew/Code/Scribe-Branches/v2.00/Utils/ScribeRecoverMail2/build/Debug/ScribeRecoverMail2.app/Contents/Frameworks/Lgi.framework/Versions/A/Lgi) ==80518== by

问题 I have a simple matrix class I've made for use with opengl (es 2.0, afaik there isn't any built in version for that particular version of opengl). It is basically nothing more than a vector which is resized to contain 16 floats in the constructor, (I chose a vector over just a 16 float array for the = operator it had), and some convenience functions that are useful in the context of opengl. Anyway, one of these convenience structures loads the identity matrix into the vector, it is: void

问题 Hi I'm running into an munmap_chunk(): invalid pointer: error in my c program. The main problem is...I'm not even sure what all of the ways a pointer can become invalid are. I've checked all over my code for strings not being calloced with enough space, but found nothing that looks like it'll run over bounds! The relevant code is below (what I THINK is the relevant code anyway) //Takes in a username and suggests friends of friends who are the opposite sex as friends of username 395 void

问题 I am writing a program that takes a list of path ( environmental variable), splits the paths and prints it. When compiling it I get a segfault. The following is my output on GDB : Program received signal SIGSEGV, Segmentation fault. 0x0000000000400eb0 in dest (name=0x7fffffffbce0 "PATH") at executables.c:100 100 dest[i] = malloc(srclen+1); On valgrind: ==21574== 1 errors in context 2 of 3: ==21574== Use of uninitialised value of size 8 ==21574== at 0x400EB0: dest (executables.c:100) ==21574==