Timeline for Cases of memory management where it is reasonable to separate program into several execs
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2020 at 19:52 | comment | added | Doc Brown | @MkKvease: I think the previous comment is spot-on. If you dug yourself into a hole and want to get out, first thing you need to do is stop digging. If you are uncertain about pointers, try to write code without them. If you don't know how, post questions about your code at Stackoverflow (but make sure you follow their rules on how to write good questions). | |
| Nov 13, 2020 at 19:02 | comment | added | RaySolva | If my problem wasn't be so strange (for me), I think I had found a solution on the surface of memory layout concepts. But I did not find, and that leaded me to thought of process splitting. Maybe I just blind, you know, everybody can become a victim of that.. | |
| Nov 13, 2020 at 18:59 | comment | added | RaySolva | @DocBrown I wrote it by myself ignoring unknown part of memory concepts, and yep, I am not very good at pointers manipulations. That doesn't mean that I don't use free() or pointers, but I use them without full understanding sometimes. Alloc & re-alloc isn't clear for me yet, so I tried not to use them at all. Previously, I'd fixed a lot of bugs causing segfaults and overflows, so kind of an intuitive understanding of basic memory restrictions I have. but my case freaks me out, I tried everything (that I know), and I can't understand what exactly I am doing wrong. GDB is new for me too. | |
| Nov 13, 2020 at 18:11 | comment | added | Doc Brown | @MkKvease: did you write the whole program, or did someone else write the parts which cause the issues? | |
| Nov 13, 2020 at 15:50 | comment | added | Stack Exchange Broke The Law | @MkKvease You can't not learn it. The most that you can do is to never free anything (a deliberate memory leak) but you still have to get everything else right. | |
| Nov 13, 2020 at 15:45 | comment | added | RaySolva | ..so I thought, that I can avoid this by splitting my entire program to independent processes, each of which will just put in and read data from temporarily files, instead of variables inside one joint memory of one active process, bypassing transfer of arguments. | |
| Nov 13, 2020 at 15:33 | comment | added | RaySolva | thank you very much, you made a great outline! I know that memory management is must have in C, and I want to learn it actually, but I want to set a checkpoint in my project and take a break due to critical affairs.. At least one of my bugs happens not in specific block of code, but because I handle function arguments badly - syntactically it's OK, but segfaults and stack-overflows continue to happen. I've tried for hours to fix it by black-box technic, but the memory 'magic' did not revealed for me. | |
| Nov 13, 2020 at 15:20 | vote | accept | RaySolva | ||
| Nov 13, 2020 at 15:47 | |||||
| Nov 13, 2020 at 12:25 | history | edited | Doc Brown | CC BY-SA 4.0 |
deleted 17 characters in body
|
| Nov 13, 2020 at 9:53 | history | answered | Doc Brown | CC BY-SA 4.0 |