Reverse Debugging in GDB 7.0

<@knife> reverse debugging?
<@knife> does that mean it puts bugs back into the program?
<@knife> :P

The new GDB version 7.0 is supposed to be released this month and will finally have reversible debugging features. It will be supported on Native i386 Linux and AMD64 along with several remote targets. GDB is every hackers favorite debugger and I am sure you will all be excited about these new commands.

• reverse-continue ('rc') -- Continue program being debugged but run it in reverse
• reverse-finish -- Execute backward until just before the selected stack frame is called
• reverse-next ('rn') -- Step program backward, proceeding through subroutine calls.
• reverse-nexti ('rni') -- Step backward one instruction, but proceed through called subroutines.
• reverse-step ('rs') -- Step program backward until it reaches the beginning of a previous source line
• reverse-stepi -- Step backward exactly one instruction
• set exec-direction (forward/reverse) -- Set direction of execution.
  All subsequent execution commands (continue, step, until etc.) will run the program being debugged in the selected direction.

Breakpoints and watchpoints will work in reverse -- allowing you for instance to proceed directly to the previous point at which a variable was modified.

http://www.gnu.org/software/gdb/news/reversible.html

http://sourceware.org/gdb/wiki/ReversibleDebugging

BotNet infected IP Ranges, BSOD fun, and the worst Star Wars costumes of all time!

Since there is nothing terribly important to post about at the moment, I will take this time to have a little fun. First of all, I am going to post a couple of funny BSOD images i found recently. ENJOI!


Next is an IP List to shift focus towards . It is a list of ranges that are repeat botnet infected servers/PC's. Some of the ranges are even /16 so it might be a lot to go through, but who knows what some research might bring. Like the forum post said...

"It doesn't take an Einstein to figure out that this IP list is like a shopping list of 'soft targets'... ie ISP's that are obviously vulnerable to being oWn3d. Heck.. they are already owN3d... or they wouldn't have shown up in this list." -courtesy of http://www.infosyssec.com/forum

third: Is this not the lamest Full Disclosure post ever?!?! I have seen some bad ones in my day, but this takes the cake.

[FD] Re: Dumb question: Is Windows box behind a router safe ? [ http://seclists.org/fulldisclosure/2009/Sep/0320.html ]

and last but not least, the worst(or best?) star wars costumes of all time. HEH!

Gay Test

if you are trying to read what that code in the background is, you might be...