Invalid assumption: void *my_realloc(void *ptr, size_t size) { unsigned char *old_ptr = (unsigned char *)ptr; You’re breaking the realloc() specification here. realloc() doesn’t assume that the ptr would always be pointing to a string. It is type-agnostic. And the cast…
It is always easier to divide program into logical bits and place them in functions. char *addToBuff(char *buff, int ch, size_t *size) { //working on local variable buff. No need for a temporary variable buff = realloc(buff, *size + 1);…
First of all and most importantly: This is not good C++ code, not even decent. For example, some of your #includes are wrong, like <stdio.h> should be <cstdio> instead. The worst thing here are those #defines that make your code…
Valgrind says that the illegal write is occurring at Address 0x6172676f72502074. If you look at that address as ASCII characters, it’s: argorP t, or converting from little endian: t Progra. This looks like part of one of your menu items,…
Shouldn’t the last line be fclose(fp)? I think that’s where things are going wrong. Change pclose(fp) to fclose(fp). fopen() -> fclose() popen() -> pclose() 0 solved Valgrind reports memory leak though there isn’t one [c]
Your initDictionary doesn’t return the pointer dictionary anywhere. That means when you do Dictionary* dictionary = initDictionary(); the value of dictionary will be indeterminate (seemingly random or garbage), and dereferencing this pointer or passing it to free will result in…
Here after is a proposed solution in main() : List of the corrected errors and enhancements: 1- in the formatting output, replace %p (dedicated to pointers) by %s (dedicated to strings). 2- before storing in the output string zeile_array[d] allocate…
There are many possible reasons, but four come immediately to mind. The IP address is invalid. The IP address is unreachable because of an error in routing table configuration on intermediate nodes. A firewall somewhere is refusing to admit the…
Valgrind shows you, that everything is all right, nothing leaked: definitely lost: 0 bytes indirectly lost: 0 bytes possibly lost: 0 bytes solved Why any executable leaks memory?