/*C*/
An example of an unprofessional-looking diagram. Still, it helped me debug code for the C programming assignment.
Ugh. I have been debugging C code for hours, and still haven’t found a way to solve my problem.
I am currently taking a course on C, for “personal enrichment,” but this unsolvable problem is very very annoying, and I wonder when I will learn at this rate. .\/.
i’m the first one to add a comment in this blog!~
| Posted 1 year, 6 months agoseems like you are ‘enriching’ your endurance~ lol
Congratulations for being the first one to leave a comment!!!!
You will be written in the emjaykim blog history book =)
Ha! enriching endurance — I wish I could test it a little less often,
Although, I finally did find out what my bug is.
I was writing down 59 instead of 57 when indexing an array of structures, thus, getting a segmentation fault! So stupid!!!
Lessons learned:
| Posted 1 year, 6 months ago1. when a problem is invisible on the screen, print out the code. Then you will see it.
2. draw diagrams.
3. think, wrong address when “segmentation fault” appears.
did you know that first bug was a ‘real’ bug?
| Posted 1 year, 6 months agohttp://en.wikipedia.org/wiki/Software_bug
Yeah, I read about that before. Isn’t it interesting how some terms in programming come about? Like C being called C because it came after B, or like GNU standing for “Gnu’s Not Unix”.
| Posted 1 year, 6 months ago