Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: krishnan gosakan <krishnan.gosakan@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Facing challenge in making some changes in GDB for my personal project
Date: Mon, 05 Aug 2019 09:43:00 -0000	[thread overview]
Message-ID: <CAHEcG95Ld12H1yD_z0GF907r5g2nR6Y6ZKxdk4j6RBebjF3GdA@mail.gmail.com> (raw)
In-Reply-To: <CAAEqJhZZ2BqyP9iO9-mnF-5aDJnyY2x5HTFc1zRQB9cJUuyzkg@mail.gmail.com>

Hi,

On Sun, 4 Aug 2019 at 19:14, krishnan gosakan
<krishnan.gosakan@gmail.com> wrote:
>
> Hi,
> This is my first message in this mailing group. I am pretty new to gdb code
> base. I am thinking of implementing something similar to findcrypt in IDA
> pro in GDB. I first tried to script it in python but it took so long that
> it is impractical. So, I decided to get the GDB source and make a few
> modifications such that I can add a new command(like run,step etc..) which
> does the same.
> This command has two parts: It should do a single step execution. After
> each step, I should disassemble the current instruction and find if any
> crypto constants are used.
> I am facing difficulty in disassembling the instructions. As far as I
> analysed the source code, there is no option for returning the disassembled
> information as some kind of object to caller. All that is available is
> functions which can print the disassembled instruction. So, I would like to
> know how I could get the disassembled instruction as some kind of object,
> which I can use for future analysis.

I'm afraid binutils' disassembler doesn't provide such in-depth
information on the instructions as their operands, affected registers
etc.: it can only format the disassembly string.
I suggest you to try a specialized disassembler like e.g. Capstone [1]
to do the analysis. I have actually used it to implement some
instruction analysis in another debugger (EDB) and, although some
quirks are sometimes required, Capstone does do its job generally.

[1]: https://github.com/aquynh/capstone

Regards,
Ruslan

> Thank you in advance for any help.
>
> Regards,
> G.Krishnan.


  reply	other threads:[~2019-08-05  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 16:14 krishnan gosakan
2019-08-05  9:43 ` Ruslan Kabatsayev [this message]
2019-08-05 20:29 ` Ruslan Kabatsayev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHEcG95Ld12H1yD_z0GF907r5g2nR6Y6ZKxdk4j6RBebjF3GdA@mail.gmail.com \
    --to=b7.10110111@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=krishnan.gosakan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox