@rici: Non-Unix programmers in the 1990s generally avoided malloc() family functions in favor of OS functions that would offer better semantics or performance, e.g. allowing programs to query the actual sizes of allocations, or having lower overhead in exchange for requiring that programmers pass free() the size of the allocation being released. The C Standard opts for a "worse of both worlds" approach, requiring that implementations expend the overhead of tracking allocation sizes, but requiring that programs needing that information also track it for themselves. — supercat 36 secs ago

Open letter to students with homework problems — ray 25 secs ago

For specific tools you might like your asking for, might be better to look at the software recommendation softwarerecs.stackexchange.com forums. Recommendations are kind of looked down on here. Plenty of material exists on porting from .net Framework to .net core already. — Hursey 41 secs ago

Why this question is marked to be closed? I don't understand why people marked it as "Needs more focus" !! IMO, This question is fairly asking for a solution that could help build concepts of many programmers like me. Please try to help by removing my blockage instead of ignoring it. Thank You. — Jatin 16 secs ago

For general help on writing code you could have a look at softwareengineering.stackexchange.com — René Jahn 41 secs ago

Please read the Open letter to students with homework problems and How do I ask and answer homework questions?. Just copy/pasting your assignments will not win you any friends. — Quentin just now

I bet you totally have a CAN bus where you can send messages... but also, it is impossible to write (quality) firmware without an in-circuit debugger. Carpenters don't make furniture while wearing a blindfold. Embedded systems programmers don't make programs without an in-circuit debugger. — Lundin 33 secs ago

Welcome to Stack Overflow. This is not a code-writing or tutoring service. We can help solve specific, technical problems, not open-ended requests for code or advice. The following references give excellent advice on debugging your code. How to debug small programs and, Six Debugging Techniques for Python Programmers — itprorh66 just now

Stack Overflow is not a code-writing service, it's a "question and answer site for professional and enthusiast programmers". So where you don't know any programming languages, sorry, you're in the wrong place. If you want to learn more about this site, take the tour [where I got that quote from]. — wjandrea 42 secs ago

Shouldn't this be posted at either software engineering or code review? — Jeff Holt 28 secs ago

Stack Overflow is not a site providing programmers doing your job for you or helping you out in this general way. Please read the "What topics can I ask about here?" Help Center page. We are not a free write-my-code service. We'll help you with specific issues in your attempt to do this; we won't just write the whole thing for you, for nothing. We are volunteers. That said your time is not more valuable than ours. We'll help those who have demonstrated first that they tried to help themselves. — Niklas E. 15 secs ago

Consider polishing up this question to observe the requirements of Software Recommendations and asking there. — user4581301 46 secs ago

Bit too vague for Stack Overflow, probably better posted on Software Engineering — Charlieface 11 secs ago

You should take the tour and read How to Ask. Stack overflow is designed to help programmers when they get stuck, not to provide a free code-writing service for non-programmers. — Quentin 27 secs ago

@rici: Code which needs to be robust when hitting memory limits shouldn't be using malloc() and realloc() during allocation, but should instead allocate storage via some mechanism that allows programs to know how much memory they will be able to allocate safely, indicate that allocations may be considered "purgeable" when not locked, or use other such mechanisms the standard library lacks. Code which is using malloc() and realloc() during operation will in many cases have no way of handling low-memory sitautions robustly, no matter how hard programmers try. — supercat 58 secs ago

@selbie super cool. Also More info for the future programmers :) — Olivia22 48 secs ago