It's too bad Red Hat didn't do anything with Code Fusion, which they got when they acquired Cygnus Solutions. Code Fusion had a special version of gdb, integrated into the Code Fusion GUI. Code Fusion was the closest thing to Borland style tools. If you hunt around the Red Hat site, you may be able to still find the source code for Code Fusion, I believe they had it there at some point.<br><br><br><b><i>Jason Turner <jturner@nonzerosums.org></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Ahh, someone is just getting real curious... :-D<br><br>Well, let me say ahead of time... no bonus points for me. But I only <br>chime in here because, selfishly, I'm curious if anyone out there would <br>recommend a particularly good interface(gui) to gdb. Which is my first <br>answer to your question about a disassembler. Now, I'm primarily an <br>emacs+gdb guy when playing with code on Linux. But I
have to admit I've <br>never been as effective with that tool when debugging source(much less <br>object) code than when I used Symantec or Borland tools on Windoze. <br><br>So, I know gdb inside emacs is not an option for you, VI guy. Have you <br>tried to dump the code into gdb on the command line and seen anything <br>helpful? I just dunno ahead of time if that would pass all your <br>stipulations. But it's cheap to try, no?<br><br>--<br>jt<br><br><br><br>jim stockford wrote:<br>> <GEEK_ALERT: this="" will="" be="" kind="" of="" weird="" for="" most="" people=""><br>> <GEEK_QUESTION: at="" end="" of="" this="" message,="" need="" disassembler=""><br>><br>> last meeting catherine suggested backing up the<br>> master boot record.<br>> i did it.<br>><br>> Here's the story:<br>> as root in a terminal window using the bash shell:<br>><br>> # dd if=/dev/hda of=./mbr bs=512 count=1<br>> i used the dd command<br>> if is the input
source. i think /dev/hda represents the<br>> entire primary master hard drive starting at byte zero<br>> of sector zero of track zero of side zero, in other words<br>> the master boot record area.<br>> of is the output, ./mbr (in the current directory, a file<br>> with a name i made up -- mbr)<br>> bs is the number of bytes to read at a time, 512, which<br>> i know is the number of bytes in the master boot record.<br>> count is the number of blocks to transfer from if to of<br>><br>> Non Geeks might want to stop here--this is how you<br>> get a backup of your system's master boot record,<br>> IF your machine is using IDE hard disks.<br>><br>><br>> the following is idle idiocy i find interesting with a<br>> request at bottom for a "real good" disassembler.<br>><br>> # ls -l mbr<br>> -rw--r--r 1 root root 512 Feb 23 19:44 mbr<br>> the ls command shows ./mbr has 512 bytes in it<br>><br>> # file
./mbr<br>> mbr: x86 boot sector, code offset 0x48<br>> hmmm, i don't know what "code offset" means,<br>> 0x48 is hexadecimal for 72 and i'm guessing<br>> this file has machine code that starts on byte<br>> 0x48.<br>><br>> # od -h ./mbr > ./mbr.od<br>> od the od -h command reads the .mbr file and<br>> outputs hexadecimal to a new file named ./mbr.od<br>> (which is 1544 bytes)<br>><br>> # strings ./mbr > ./mbr.strings<br>> strings the strings command outputs any ASCII<br>> sequences that are in the ./mbr file to a new file<br>> that I've named ./mbr.strings (which is 48 bytes).<br>> The contents are<br>> LILO<br>> ZREfI<br>> D|f1<br>> GRUB<br>> Geom<br>> Hard Disk<br>> Read<br>> Error<br>> Well, to me that seems like the kind of strings that<br>> ought to be in the master boot record.<br>><br>> # vi ./mbr<br>> well, it looks like martian, all right.<br>> okay, i know i'm a
maniac, but hey! the vi editor<br>> can edit anything.<br>><br>> # vi -b ./mbr<br>> this looks a little better, but only a little (the -b<br>> option tells vi it's working with a "binary" file).<br>><br>> # dis<br>> -bash: dis: command not found<br>> damn! the dis command was on ATT sysVreviii<br>> where's a disassembler when you need one? <-- geek question<br>> there are lots, but which is real good? <-- bonus geek question<br>> for me, "real good" is probably "real stupid" in that it will not<br>> fail on any input for any reason, does not expect ELF or other<br>> header data, just takes a byte stream and generates mnemonics<br>> for any machine code it finds; i've got 32-bit iAPX86 stuff.<br>><br>> ever hopefully,<br>> jim<br>><br>><br>> _______________________________________________<br>> sf-lug mailing list<br>> sf-lug@linuxmafia.com<br>>
http://linuxmafia.com/mailman/listinfo/sf-lug<br>> <br><br>_______________________________________________<br>sf-lug mailing list<br>sf-lug@linuxmafia.com<br>http://linuxmafia.com/mailman/listinfo/sf-lug<br></GEEK_QUESTION:></GEEK_ALERT:></blockquote><br><p>