Which nobody posted here

And?

If you want you can send one yourself

The same for you: and? I'm not responding the op, i responsed the (wrong) answer

I am responding to you. You care more about someone's answer, so do it yourself. 1. It's not harassment to ask someone to google. 2. It's considered good practice to not spoonfeed people. 3. If you feel like someone has given a "wrong" answer, answer them yourself the way you like it rather than demanding others to do so. 4. No one's ansking you to send a complicated example, send a simple one. If it's incorrect we'll correct you, you'll learn a few things, they'll learn a few things, even we could learn from it. Everyone benefits.

The point 1 is false. It's considered rude to ask someone to google. If you don't want to answer, don't answer. It's the equivalent of "don't ask to ask". Evidence: unix stackexchange: https://unix.meta.stackexchange.com/questions/7089/why-is-it-if-anyone-asks-a-question-no-one-can-ever-just-give-the-answer-for-th

I am responding to you. You care more about someone's answer, so do it yourself. 1. It's not harassment to ask someone to google. 2. It's considered good practice to not spoonfeed people. 3. If you feel like someone has given a "wrong" answer, answer them yourself the way you like it rather than demanding others to do so. 4. No one's ansking you to send a complicated example, send a simple one. If it's incorrect we'll correct you, you'll learn a few things, they'll learn a few things, even we could learn from it. Everyone benefits.

Point 2, false: Don't create a group for help people with programming questions if you don't be able to spoonfeed them. Some topics are obscure or unknown and spoonfeed is the only good practice. The good practice is "don't assume everybody will know how a profiler is or what massif is, without prior knowledge before". No quotes, international group and all levels of english would mistranslate massive with massif, with no indication it's a program itself

I am responding to you. You care more about someone's answer, so do it yourself. 1. It's not harassment to ask someone to google. 2. It's considered good practice to not spoonfeed people. 3. If you feel like someone has given a "wrong" answer, answer them yourself the way you like it rather than demanding others to do so. 4. No one's ansking you to send a complicated example, send a simple one. If it's incorrect we'll correct you, you'll learn a few things, they'll learn a few things, even we could learn from it. Everyone benefits.

I was being catched for Cunningham, I has no knowledge about profilers. I didn't know what "massif" is prior to that comment

It will beneficial for him/her someone could show an example. Not everybody will find themselves everything they need... that's why zahra asked here

The op hasn't even shared their code, all we know is that they get an error for allocating too much. If we even want to give an example it would be too generic in their case. The best thing imo is for the op to see the software for themselves, try it out then come back here with better informed questions

I actually didn't see the message above about the bad alloc, that changes things since that can probably be caught with just a debugger. Basically what Danya wrote just before my message

"What part of the code" is a really good question to start with, and "how" really depends on it. Most of the time it is unreasonable to try optimizing everything (may end up optimizing 1% of memory while 90% of it is accidentally eaten by some not-fixed bug). I recommend finding a memory profiler that suits your needs. For example, if you can use Valgrind it has "massif" memory profiler included. Valgrind also includes tools to check for memory leaks (when you allocate memory and never clean it), which may contribute to high memory consumption as well. https://postimg.cc/v1rp7S7H Here's an example from massif-visualizer that I've just run on one of my tests, I could quickly see that I have some render data that eats up most of the space, and I know that's a bug because render should be disabled so this data shouldn't even be there. Your case may be more complex than this, but having a good tool for this in your toolbox may make it much easier to reason about these problems.

What site should I use to do this and learn it? As you posted in the picture

Hello kings and queens I'm ur fellow mate looking a way to learn C can anyone recommend something like videos playlist or any course my goal is to atleast intermediate level of C I like hindi or English or Spanish videos I can't understand other languages

No a debugger can't help with this problem. Bad alloc happens when memory has already been exhausted. So problem could be somewhere else in the code. So like I said, he has to go through all his memory allocations and deallocations to see that everything is in order using tools like valgrind or a memory tracker

Most likely the cause will be the same allocation that fails. Not guaranteed of course, especially in a big app, but I would start with that.

Hello kings and queens I'm ur fellow mate looking a way to learn C can anyone recommend something like videos playlist or any course my goal is to atleast intermediate level of C I like hindi or English or Spanish videos I can't understand other languages

hey everyone... I just wrote a piece of code which included this: cout<<' '; (I pushed space button twice between ") the output was 8224 I couldn't understand why... does anyone know the reason ?

Which one is better, one call to read/write entire buffer or multiple read/write calls until end of buffer?

At their core, API calls that read, or write, an entire buffer are usually internally implemented by calling the API that reads, or writes, in bits, till the entire buffer is read from, or written to. The API that reads or writes the whole buffer is provided for convenience, and will do the scaffolding and sanity checks (error detection, pre and post contract conditions, etc) for you. Now, which to use? If you need all the data in the buffer before proceeding with your algorithm, then consider the API that reads, or writes, in whole. If you can use bits of the data as it comes in, then maybe the API that reads, or writes, in bits may be your preference.

Which one is better, one call to read/write entire buffer or multiple read/write calls until end of buffer?

hey everyone i am looking for video in resources group but there are no videos over there.... a  playlist would be helpful  who teaches C till intermediate  level if anyone has any pm me or just recommend in the chat

There is no good English courses

So which lang?

Russian

Russian lang is very difficult 😂 I'll take months and months to learn it

Russian

/start@MissRose_bot

/start@MissRose_bot

Hi guys I recently decided to remember my old skills of writing in C++, got to threads and caught unexpected behavior. Console messages are printed in the correct sequence, but with incorrect delays. Namely, HERE3 is printed only after 10 seconds, that is, after the delay on line 16 is performed. What could be the cause of the problem? MacOS 14, M1 Pro, GCC13 (brew)

It is not weird. That is the behavior I would expect on most implementations that buffer the output. The problem is that while printing HERE3, you don't use std::endl. So though the write has been processed, it is still sitting in the output buffer waiting for the output buffer to become full. On implementations where standard output is line buffered, you can see HERE3 printed earlier by just adding a \n. std::endl would work always

who is looking for a programmer?

Hi, the executable of my project is in a folder inside the build folder. The executable needs to read some files from another folder within the same project. It works fine when providing the specific path from the executable to the files. However, if I move the executable to another folder, the code doesn't work anymore. I've looked into absolute paths, etc. Do you have any advice?

Hi, the executable of my project is in a folder inside the build folder. The executable needs to read some files from another folder within the same project. It works fine when providing the specific path from the executable to the files. However, if I move the executable to another folder, the code doesn't work anymore. I've looked into absolute paths, etc. Do you have any advice?

who is looking for a programmer?

however, this leads to UB as memory is uninitialized and my get_length method, which counts chars until it encounters'\0' doesn't work with this my question is what should i initialize my memory with? note that according to the task the only member of the class i am allowed to have is the pointer (m_strptr), i cannot store the length in the class.

With new char[n]{}, it will help you initialize the array to all '\0'.

hi guys, i'm writing a custom string class as an assignment. currently my constructor for a string of length n looks like this: MyString(size_t n) { char *ptr = (char *)malloc(n + 1); ptr[n] = '\0'; m_strptr = ptr; std::cout << m_strptr << "\n"; }

Maybe you could modify the constructor to take a padding character as a parameter (and make it default-valued). BTW, it is more intuitive to allocate a n+1 array for a string of size n.

I changed the constructor to this now: MyString(size_t n) { char *ptr = (char *)malloc(n + 1); memset(ptr, '-', n); ptr[n] = '\0'; m_strptr = ptr; } which sets all characters to '-' as a placeholder lol. i don't know what's the best practice for this but i guess my task does not prohibit that any way to improve it?

I changed the constructor to this now: MyString(size_t n) { char *ptr = (char *)malloc(n + 1); memset(ptr, '-', n); ptr[n] = '\0'; m_strptr = ptr; } which sets all characters to '-' as a placeholder lol. i don't know what's the best practice for this but i guess my task does not prohibit that any way to improve it?

yes and i don't want that because the way i check for the length is by seeing when is '\0' encountered for the first time: size_t get_length() { size_t n = 0; while (m_strptr[n] != '\0') { n++; } return n; }