Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 37

Thread: Linux debugger

  1. #16

    i also only find sources for dis-/assembling stuff, which is quite well covered allready in the OSS/FS world, I think these sources don't give too much for a new linux debugger imho.

    regards, 0xf001

  2. #17
    Quote Originally Posted by naides
    At click the link Sources
    THat's just the sources for an assembler and disassembler. It's far from a complete debugger. It's useful but similar materials are available on the internet.

  3. #18
    Quote Originally Posted by LaptoniC
    I am very newbie when it comes to linux RCE.I need to debug linux binaries.I need your help to get it started.First of all what linux distro is debugger friendly.I think to install ubuntu.I have tried to download knoppix|Re but couldn't found the download link at Second what debugger is more userfriendly(ollydbg style gui etc) and easy to install.I never used IDA in linux envrionment but I guess it has linux debugger too.I have read 0xf001's page and there are several debuggers so if you can help I will appreciate.Thanks.
    for a userland debugger w/ 'GUI', check out gdbtui (part of every gdb 6.x release i think), for a kernel debugger there's rr0d (multi-OS).

  4. #19

    Well I ditched WinXP alltogether, and switched to Linux full time around the start of this year. Anyhows my most missed Win32 app is OllyDbg :\.

    Anyhows I just started looking into reversing on Linux again, and are quite interested in coding my own Debugger, kinda like OllyDbg. Well I don't think I could do something as good as OllyDbg, it's just great. I'm not to sure about things yet, kinda got another project to work on.

    For the GUI, I think I'd use FLTK (, checkout these nice tutorials for learning it. See

    BTW, I just ran into these (what I think) are nice tutorials for reversing in Linux, well have not gone through them properly yet. See AND (look at em in the Print View ). Hmm, maybe they have already been mentioned on these forums?

    Last edited by yosh64; June 11th, 2006 at 13:53.
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  5. #20

    thx for the links, to be honest the securityfocus articles are very disappointing, I did not find this teaches anything
    [edit] ok, the 2nd link is better

    check maybe this one
    and this one:

    GUI was meant here as the GUI for the debugger. gdbtui is a bit very text mode, and I'd prefer
    gdb with mammon_s gdbinit file - is far more usable than anything else

    regards, 0xf001

  6. #21

    Thanks for your concern and posting them links for me . Well I looked into reversing on Linux a little bit ages ago (when just getting into Linux full time), and had come accross your page, and mammon_'s gdbinit at the time . Even so, I did find it tricky, coming from OllyDbg... so yea kinda lost interest, well until now. Hopefully I can continue futher, I'd really like to beable to do Win32 crackmes in Linux.

    Well at the time I also ran into... (btw, after just taking a peek at "SecurityWarrior.pdf", I found this website refered at the bottom also), AND AND So maybe these will be useful to someone? or maybe yas know of em already?

    BTW, I had never come accross before , hehe.

    Last edited by yosh64; June 11th, 2006 at 15:21.
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  7. #22

    I like that, please keep posting interesting links as you find them!

    And its true, when beeing used to sthg like _ollydbg_ then ... its a bit hard to find something similar, on the other side its "just another learning curve" to get used to more textmode work, and "utility chains" - if one would consider this as an option
    however, it's cool you give linux another shot hehehe

    cheers, 0xf001

  8. #23
    try Totalview

  9. #24
    Hey everyone, I'm relativly new to this forum, but I do do work in the reverse engineering field. Ollydbg is clearly the debugger of choice for windows, but like you I have found no linux debugger which really steps up to the plate.

    So i am making my own debugger, and it is designed from the start to be cross platform (a single c++ class defines all debugger primitives which are OS specific, the rest is all QT).

    I don't know when I will be releasing my first version, but i really hope sometime in the next 2 months I'll have _something_ worth using out the door.

    For some more basic info, and screenshots of what I have so far, check out my page:

    Visually it's always there, I'm working on my custom QDissasemblyView widget at the moment, and it currently has a ptrace impementation for the basic functionality.

    Once I am nearing a 1.0 release, I plan to open source it, and hopefully make a very positive contribution the RE community


  10. #25
    I try it.thx.

  11. #26
    hi proxy

    i hope you finish this project!!! (this is what ppl tell me also )

    ok I see you use ptrace() - which is .... well ... mabye checkout this:, I think it's worth an evaluation, but
    of course just code as you like it!!

    respect ,


  12. #27
    proxy > Wow ! Really good idea, you're courageous.
    Hope this will be out soon
    keep up the good work
    Please consider donating to help staying online (here is why).
    Any amount greatly appreciated. Thank you.

  13. #28
    hi again,

    proxy - check this - i saw you plan to work on things like

    - code analysis
    - byte pattern search

    well I have an "independent" implementation of a quite nice code search etc allready ... maybe you'd be interested in that? I have the idea to make a libreview - which provides you with an API for that. Only dependency is libdisasm from mammon_. did you check that out? i am interested how you decode opcodes, too
    I'd like to share thoughts, it seems you are a good coder. I use Qt3 still btw

    regards, 0xf001

  14. #29
    linhanshi: sorry, no release yet, I wanna take my time and make sure it's worth using before I put it out the door, but i'll post in this forum as soon as I do

    0xf001: firstly, remember, that all the core debugger functionality is isolated from the rest of the debugger, so using ptrace is more of a "get off the ground" thing, not perminent. beating anti-debugging techniques is not on the top of my todo list, but it's in there, so maybe once the rest of the debugger is up to speed, i'll replace the ptrace core with a more robust one (does linux's proc debugging interface have the same diffiencies?)

    also, yes i DO use libdisasm, it's a good lib.

    I've also read about your review project and i like it. I would definitely be intererested in a library version of it. I already have implemented a basic byte pattern searcher called bgrep (it's a command line utility) found on my coding page: But as far as code analysis, i definitely will need some help in the future.

    thanks for the support guys, it's a real motivator. I'll keep this forum up to do date on my progress as things move along.


  15. #30

    @proxy: I hope your debugger is coming along well .

    Anyhows I just wanted to say that I am about to start on my own Linux ELF debugger. Personally I just hope to beable to reverse Win32 CrackMes with it through Wine, in a manner alike OllyDbg.

    I'm firstly gonna start with a linux ELF disassembler, then move onto the actual debugger. I hope to make it alike OllyDbg, well maybe a few changes. One pretty cool idea I got is to beable to take and compare snapshots on a specified range of memory, or just on a specific section. Well in Win32 I just used TSearch for such things. But I won't worry about anything special until I have the basics down solid. Anyhows I think the disassembler is gonna take some time, as there are alot of x86 instructions.

    One thing I thought was interesting about debugging Win32 apps through Wine on Linux, is that I think a few of Win32 specific anti-debugger tricks will be gone? Well just a quick thought, maybe I'm wrong... I don't really know to much on the subject, maybe it will just be IsDebuggerPresent()???

    I do have a question about brakepoints... Well I think this would answer a number of questions I have... I was wondering how brakepoints were set on memory, as done in OllyDbg? Well it makes me think that every instruction executed is done through the debugger (so the debugger would beable to check on every byte to be MOV'd to/from memory, and everything else). It's just that I used to do (made a little few loaders) alike seen at Where you set hooks at the address you wish to break at by changing the instructions to EB FE (so gets stuck in tiny'est loop), and you constantly read in the registers and check if EIP has hit the address of your breakpoint.

    Anyhows that's all, hopefully I can stay with this project .

    Last edited by yosh64; June 23rd, 2006 at 13:40.
    I promise that I have read the FAQ and tried to use the Search to answer my question.

Similar Threads

  1. Replies: 3
    Last Post: August 12th, 2008, 14:59
  2. bidirectional Linux debugger
    By gabri3l in forum Linux RCE
    Replies: 1
    Last Post: September 5th, 2006, 23:38
  3. Linux Flexlm SDK Kit
    By roZes in forum Advanced Reversing and Programming
    Replies: 0
    Last Post: May 22nd, 2001, 01:57
  4. Linux
    By Sorvat in forum Advanced Reversing and Programming
    Replies: 1
    Last Post: April 30th, 2001, 21:07


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts