WTF, GDB?

Why the fuck doesn't it understand that

break 0x401000

means [i]I want the bloody breakpoint at address 401000h[i], not "there's no function with that name"? No language you'd sanely use it with will even allow you to name a function starting with a digit (that's why C makes hex constants start with 0 - to distinguish them from identifiers!) and in the very perverted case such a symbol actually ended up in an object file you could always escape using quotes:

break "0x13371337"

Should mean "I really do want to put a breakpoint on a symbol with such a fucked-up name." Idiots...

GDB stands for God Damn Bugger.

SoftICE > DEBUG > WinDbg >>> OllyDbg >>> GDB

>>3
I'm damn well aware of that but why the jesusfucking mary can't it figure out that if I'm entering a number IT IS VERY BLOODY LIKELY GOING TO BE AN ADDRESS and default to that?!?!?

This is as fucked up as gas's random asterisks everywhere that make no sense. At least we have fasm and nasm to get around that repulsive beast, but where's the equivalent for gdb?

Reminds me of this quote from some anon:
gdb will make you a better programmer, since you'll be so reluctant to use it you'll be careful to not write buggy code.
Except in this case I'm debugging someone else's code. Fuck.