full-disclosure - Step-by-step instructions for debugging Cisco IOS using gdb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <46d5a9ed0808151120j54d980d2lcb085c0de5d93d07@mail.gmail.com>
Date: Fri, 15 Aug 2008 19:20:18 +0100
From: "Smiler S" <smiler808@...glemail.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Step-by-step instructions for debugging Cisco IOS
	using gdb

 From: Andy Davis
<iosftpexploit_at_googlemail.com<iosftpexploit_at_googlemail.com?Subject=Re:%20Step-by-step%20instructions%20for%20debugging%20Cisco%20IOS%20using%20gdb>>

Date: Tue, 12 Aug 2008 22:01:37 +0100

>Congratulations you are now debugging IOS ;-)
>One unusual feature, which I have yet to explain is that when the
>registers are displayed they are all offset by 1 e.g:

If a vector variable is stored in a register, gcc writes debug information
telling gdb which register the variable is stored in. This mapping is
changed between gcc2 & gcc3. Since there isn't anything in the debug output
to distinguish code compiled by gcc3 from code compiled by gcc2, there is no
way for gdb to know the right map. gdb supports the gcc3 map.

If vector code is compiled by gcc2 as in the case of IOS, then the register
assignment will be off by 1.

PS  - Stop ripping Gyan and Varuns IOS research work you jackass cause you
ain't getting no fame with that bullshit :P :P :P

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/