really, you know, advanced stuff like, oh, this buffer hasn't been initialized. And how do you know that? It might be difficult to tell. You know, it can get very, very sort of detailed. It's not always the friendliest kind of error messages. Sometimes it's just, it's you and a bunch of Xs and zeros. And hopefully you kind of can grasp maybe what's going on. Sometimes you can't and that's okay. I mean, sometimes just the backtrace will be enough for some other developer to look further into the process. Other times you might be able to figure out what's going on. And who knows? I mean, you might even be able to fix it. So that's GDB. To leave GDB prompt, you type in QUIT. Q-U-I-T. Okay, so I forgot to mention that. And yeah, that's for C and C++. So if it's not C or C++, you probably won't have as much success with GDB as otherwise. Let's see, is it time for a coffee break? I feel like it's time for a coffee break, but the same can be said of me at any point during the day. Actually, (25/33)
You are viewing a single comment's thread from: