Octacone wrote:
A simple bug is not going to stop me for working on my dream project. Right now I am going trough all of my code fixing everything I can see, also the bug has gone away.
Good, it shouldn't.
Octacone wrote:
Why would you think I'd be trolling? That is such nonsense.
It might seem at first like I have no clue what is going on, I don't quite have a clue when it comes to this specific case, but generally speaking I do indeed.
As I said, based on the replies in _this_ thread. It might as well be because of lack of experience. Trolls often employ techniques such as:
- Vague responses
- Omitting key details
- Not answering all questions
- etc
You've done all three in this thread, and trolls use all three to ensure things don't progress forward, or at best do so slowly. For instance if you post a picture of two side by side dis-asm's, it would be useful to actually say what those are and which is which, without somebody having to ask. Of course simple mistakes happen..
I think at least a few times you didn't answer some questions, though in one case at least you responded to it significantly later, which also helps to create confusion.
I'm not saying you are a troll, just that this thread started to appear as such.
Octacone wrote:
My debugging skill are not as good as yours but I am trying, this is actually the first time I've used GDB, ever.
Unless you do extreme unit testing, a debugger (gdb or something else) is your best friend. Even if you ignore all the fancy stuff, the very basic feature of being able to check register contents and single-stepping is all you really need, and that doesn't require gdb knowledge. Of course you will very quickly get tired of single-stepping which is where break points come in, but still no gdb knowledge required.
I'm no master at _gdb_, but debugging isn't really tied to a specific debugger. You just need to follow the flow of code to understand why something is happening and then work backwards. Also having gdb print the C code along with the dis-asm while single stepping does help, even if you don't fully understand all asm.
Octacone wrote:
It seems like you don't understand how paging works either, because you are questioning my design choices without even ever taking a look at it fully.
None of us have seen all of your code, so are you suggesting none of us should have responded?
I was commenting based on what I have seen and what I can extrapolate from that. I'm guessing that you are likely doing something overly complicated with no good benefit. If you look at the example code in the paging part of the Wiki you should see that paging is actually very simple. It's usually different types of optimizations that may make it more complex, but you shouldn't attempt _any_ optimizations to paging until you actually have it working.
Octacone wrote:
Sorry if this thread looks "dumb" to you, but that is how trial and error looks like.
Trial and error is not a good way to solve anything, especially when done in this manner. From my perspective it seemed like you wanted to try _anything_ that might work, and you shouldn't. You should try to understand the problem and then fix it. Often we think trying random things is easier/faster, but in reality it's often (almost always) more beneficial to stop, learn, then fix. But we tend to think the learning will take too long and thus want to skip it.
Note, this is pretty much the problem in politics as well, let's try random stuff then at least we can say: "we did _something_", too bad something random isn't likely to yield the wanted outcome.
Octacone wrote:
Since I fixed the bug by properly allocating strings (bunch of them actually) I mark this topic closed. @LtG if you have any further question feel free to PM me.
Probably a good idea to drop this thread, allows the next to start fresh at a specific problem.. As for PM, I usually avoid those as they don't contribute as much to the public knowledge base.. Similar to in some cases people reply to their own threads: "I solved it!", which is incredibly annoying two years later for the next guy who now believes a solution exists but doesn't get to know what it is =)