News for hackers. Stuff that matters.
Re:Redis crashes - a small rant about software reliability by jgrahamc on Tuesday November 27, 2012 @09:02AM (#4837104)
His point about logging registers and stack is interesting. Many years ago I worked on some software that ran on Windows NT 4.0 and we had a weird crash from a customer who sent in a screen shot of a GPF like this: http://pisoft.ru/verstak/insider/cwfgpf1.gif

From it I was able to figure out what was wrong with the C++ program. Notice that the GPF lists the instructions at CS:EIP (the instruction pointer of the running program) and so it was possible by generating assembler output from the C++ program to identify the function/method being executed. From the registers it was possible to identify that one of the parameters was a null pointer (something like ECX being 00000000) and from that information work back up the code to figure out under what conditions that pointer could be null.

Just from that screenshot the bug was identified and fixed.

Re:Redis crashes - a small rant about software reliability by danielweber on Tuesday November 27, 2012 @11:11AM (#4837550)
I remember generating .map files as part of the build process that were invaluable in figuring out where Windows desktop programs were crashing. It was about 30 minutes of work that made 3-hour debugging sessions into 10 minute debugging sessions from then on.
Re:Redis crashes - a small rant about software reliability by malkia on Tuesday November 27, 2012 @09:46PM (#4840731)
Unfortunately address space randomization techniques make this much harder.
Re:Redis crashes - a small rant about software reliability by geal on Wednesday November 28, 2012 @03:25AM (#4841552)
Not necessarily. The screenshot indicates the bytes pointed by the IP, so it would still be possible to find them a binary you just built, and debug it from there.
Re:Redis crashes - a small rant about software reliability by malkia on Wednesday November 28, 2012 @12:28PM (#4843637)
only if this is nota relocated code, and still there can be much code duplication, especially with C++ templates/inlines