From: "Oğuzhan Eroğlu" <rohanrhu2@gmail.com>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDBFrontend
Date: Mon, 11 Apr 2022 17:23:55 +0300 [thread overview]
Message-ID: <CAM=wM24rj91rwpM4AdgQCeG8izfu5uMmwjaVgjSGS35zyxgu8g@mail.gmail.com> (raw)
In-Reply-To: <CAGP6POJHJ2OubN3QYh_eGOgPxHMhnw5kjzz1iNGphwDHgNXtMg@mail.gmail.com>
Thank youu tooo
Hongyi Zhao <hongyi.zhao@gmail.com>, 11 Nis 2022 Pzt, 15:35 tarihinde şunu
yazdı:
> On Mon, Apr 11, 2022 at 6:48 PM Oğuzhan Eroğlu <rohanrhu2@gmail.com>
> wrote:
> >
> > Hiiii, it has HTTP and WebSocket APIs to communicate from other tools.
> Also you can write plugins with using GDB-embedded Python API and you can
> add custom HTTP APIs and call them from your tool.
> >
> > You may want to look at this tutorials:
> > https://rohanrhu.github.io/gdb-frontend/tutorials/makefile-integration/
> > https://rohanrhu.github.io/gdb-frontend/tutorials/plugin-development/
> >
> > If you need a non-existent API for your integration, feel free to tell
> me or it would be nice if you could add the required API.
>
> Thanks, I'll check it out.
>
> Yours,
> Hongyi
>
> > Hongyi Zhao <hongyi.zhao@gmail.com>, 11 Nis 2022 Pzt, 04:54 tarihinde
> şunu yazdı:
> >>
> >> On Sun, Apr 10, 2022 at 9:41 PM Oğuzhan Eroğlu via Gdb
> >> <gdb@sourceware.org> wrote:
> >> >
> >> > Hiii, you can add my GDBFrontend thing to GDB's page.
> >> >
> >> > Github: https://github.com/rohanrhu/gdb-frontend
> >>
> >> Nice tool. I'm not sure if this can be integrated with Emacs.
> >>
> >> Hongyi
> >
> >
> >
> > --
> > Oğuzhan Eroğlu
> > http://oguzhaneroglu.com/
>
--
Oğuzhan Eroğlu
http://oguzhaneroglu.com/
prev parent reply other threads:[~2022-04-11 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 13:12 GDBFrontend Oğuzhan Eroğlu
2022-04-10 19:38 ` GDBFrontend Joel Brobecker
2022-04-11 1:53 ` GDBFrontend Hongyi Zhao
2022-04-11 10:48 ` GDBFrontend Oğuzhan Eroğlu
2022-04-11 12:35 ` GDBFrontend Hongyi Zhao
2022-04-11 14:23 ` Oğuzhan Eroğlu [this message]
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='CAM=wM24rj91rwpM4AdgQCeG8izfu5uMmwjaVgjSGS35zyxgu8g@mail.gmail.com' \
--to=rohanrhu2@gmail.com \
--cc=gdb@sourceware.org \
--cc=hongyi.zhao@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).