WTF, gdb!? (part n)

Program received signal SIGSEGV, Segmentation fault.
0x0000000001973fb0 in some_function ()
(gdb) disas 0x1973fb0
Dump of assembler code for function some_function:
0x000000000197011a <+0>: ...

What the fuck is wrong with this dysfunctional piece of shit!? I tell it to start disassembling at 0x1973fb0 and it decides to start at 0x197011a, twelve thousand bytes away!? Which one of the GNU idiots even thought this could be considered sensible behaviour?!?!

FUCK GNU!

>>16
x/Ni addr
will examine N instructions at addr

gdb is primarily a source code debugger, 'disas' may not work correctly if you don't have debug information or source available (and especially in a stack trace on some release built program without frame pointers for example).

This display and output of gdb can be completely customized, you can pipe it to external text processing programs and get back whatever format you want.
There's also the TUI where you can get a "gui like" view,
try:
lay asm
lay reg

And you get a bit nicer interface with a split view for registers, disassembly and command input.