tag:blogger.com,1999:blog-304267073920548108.post7105187973302486174..comments2023-07-20T15:12:50.996+03:00Comments on flux: kill 'em allUnknownnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-304267073920548108.post-78695787672001421192008-01-22T19:49:00.000+02:002008-01-22T19:49:00.000+02:00@anonymous: ah, thanks, that explains things.@mis...@anonymous: ah, thanks, that explains things.<BR/><BR/><BR/>@misha: thanks :)<BR/><BR/><BR/>@slippery-pete: in academia, amongst some there really is an emphasis on making sure the code is correct beforehand so debugging will less of a necessity. Of course they're partially right, and debugging should be less necessary than it is today, using formal methods and such. But, today we still need gdb.<BR/><BR/>@riku: ah, thanks. good point about static checking, indeed many bugs hide in error paths where they are never tested. we always compile -Wall -Werror for that reason. gcc 4.x is pretty good at that.djcbhttps://www.blogger.com/profile/15938154009846040711noreply@blogger.comtag:blogger.com,1999:blog-304267073920548108.post-62911387761934077612008-01-22T11:35:00.000+02:002008-01-22T11:35:00.000+02:00Great article! some minor points:native-gdb is a a...Great article! some minor points:<BR/><BR/>native-gdb is a arm binary to debug arm target binaries.<BR/><BR/>cross-gdb is a x86 binary that debugs arm target binaries.<BR/><BR/>cross-gdb faster and require cpu transparency, but doesn't support everything a native gdb does. It's default merely due to historic reasons, ie when qemu did not work well enough to run qemu and people didn't want to bother setting up sbrsh just to debug.<BR/><BR/>As for static vs runtime testing, valgrind/gdb will never catch bugs that happen not be in the codepaths of normal usage testing. Since usage testing tends to repeat testing the same codepath over and over, the coverage of runtime testing might be surprisingly small. Especially the error paths (where lots of bugs lurk!) will fail to be very hard to notice using valgrind.Riku Voipiohttps://www.blogger.com/profile/11009374403959477488noreply@blogger.comtag:blogger.com,1999:blog-304267073920548108.post-21414245558833242992008-01-22T00:11:00.000+02:002008-01-22T00:11:00.000+02:00"Although armchair computer scientists snuff at th..."Although armchair computer scientists snuff at the use of debuggers, down here in the trenches, it's often our last hope."<BR/><BR/>Computer Scientists often stress the importance of debugging tools. What are you talking about?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-304267073920548108.post-46759985462313364782008-01-21T18:11:00.000+02:002008-01-21T18:11:00.000+02:00Great article, Dirk.Great article, Dirk.Mishahttps://www.blogger.com/profile/08158792631664654421noreply@blogger.comtag:blogger.com,1999:blog-304267073920548108.post-66234910922978072962008-01-20T13:06:00.000+02:002008-01-20T13:06:00.000+02:00> the maemo-debug-scripts package, which (among ot...> the maemo-debug-scripts package, which (among others) offers native-gdb. I'm not sure what's so 'native' about it, but it provides gdb 6.6, which works much better than the apparently 'non-native' gdb 6.4<BR/><BR/>Native = the one installed to the Sbox target (as a maemo-debug-scripts dependency), non-native = the one provided by Sbox<BR/><BR/>maemo-debug-scripts is also available for OS2007, but with older version of Gdb I think.Anonymousnoreply@blogger.com