valgrind

I have a class in which I implement the singelton design pattern. I know some people don't think its a good idea, but it helps a lot, Anyway - I have a memory leak and vlagrind points me to these lines: _singleton = new Manager(); //Manager::instance() (Manager.cpp:18) And Manager::Manager() : _file(new ofstream), _tasks(new map<int, Task *>()), _idState(new map<int, int>()), _closing(false), _pending(false), _lock(new pthread_mutex_t), _endLock(new pthread_mutex_t), _cond(new pthread_cond_t), _flushCond(new map<int, pthread_cond_t *>()), _attr(new pthread_attr_t) { //The last line is line 25

Can you please tell me how can I use valgrind for memory profile? The article I found from google talks about how to use valgrind for memory leak. I am interested in how to use that for memory profiling (i.e. how much memory is used by what classes)? Thank you. You can use valgrind's Massif tool to get a heap profile. This code is still labelled "experimental", and it does not ship with all versions of valgrind. You may have to download and build from source. Also note that the heap profile is organized by allocation site, which is a finer granularity than classes. If you need information

Lubuntu 15.10 I have project with memory leaks. I can find them, so I cleaned up my main.cpp file, and now it looks like this: int main() { return 0; } When I check memory with the command: valgrind --leak-check=full --show-leak-kinds=all ./MyProgram > log1.txt 2>&1 I got these errors: ==5219== ==5219== LEAK SUMMARY: ==5219== definitely lost: 0 bytes in 0 blocks ==5219== indirectly lost: 0 bytes in 0 blocks ==5219== possibly lost: 728 bytes in 18 blocks ==5219== still reachable: 44,676 bytes in 224 blocks ==5219== of which reachable via heuristic: ==5219== newarray : 832 bytes in 16 blocks =

I have this C program compiled with either gcc test.c or clang test.c : int main (void) { return 0; } valgrind ./a.out gives me this: ==9232== Memcheck, a memory error detector ==9232== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==9232== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==9232== Command: ./a.out ==9232== ==9232== Conditional jump or move depends on uninitialised value(s) ==9232== at 0x4017876: index (in /usr/lib/ld-2.16.so) ==9232== by 0x4007902: expand_dynamic_string_token (in /usr/lib/ld-2.16.so) ==9232== by 0x4008204: _dl_map_object (in

First, I know similar questions have been asked. However, I'd like to have a more general simple question with really primitive C data types. So here it is. In main.c I call a function to populate those string: int main (int argc, char *argv[]){ char *host = NULL ; char *database ; char *collection_name; char *filename = ""; char *fields = NULL; char *query = NULL; ... get_options(argc, argv, &host, &database, &collection_name, &filename, &fields, &query, &aggregation); Inside get_options : if (*filename == NULL ) { *filename = (char*)realloc(*filename, strlen(*collection_name)*sizeof(char)+4)