Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gopi Kumar Bulusu <gopi@sankhya.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Cc: Michael Eager <eager@eagercon.com>
Subject: Re: [PATCH] gdb/MicroBlaze: Add support for native linux gdb
Date: Tue, 26 May 2026 17:03:24 +0530	[thread overview]
Message-ID: <CAL1P33ys5M-dsBDJ5U1tnUXkbhLTeZT46KOad8vMgJ+M+MbWDg@mail.gmail.com> (raw)
In-Reply-To: <CAL1P33wvSyEkqa5KC8QH3KRN1hGGn2-H6sE59rRjsrLibprvKg@mail.gmail.com>

[ Please note: the typo, including core target support ]

On Tue, May 26, 2026 at 5:02 PM Gopi Kumar Bulusu <gopi@sankhya.com> wrote:
>
> namaskaaram
>
> Attached is a patch to add native linux support for gdb including
> cache target support.
>
> The patch has been sanity tested on a linux instance running on qemu (runqemu).
>
> Some commonly used debugger functions such as breakpoints, step, next,
> finish, print were tested to be working.
>
> The original sources for the patch come from Xilinx/AMD Yocto git
> repository (2025.2)
>
> These went through some editing as well as some refactoring.
>
> dhanyavaadaaha
>
> gopi

  reply	other threads:[~2026-05-26 11:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 11:32 Gopi Kumar Bulusu
2026-05-26 11:33 ` Gopi Kumar Bulusu [this message]
2026-05-29 14:56 ` Tom Tromey
2026-05-29 15:01   ` Simon Marchi
2026-06-01  6:30     ` Gopi Kumar Bulusu
2026-06-01  6:38   ` Gopi Kumar Bulusu
2026-06-02  0:28     ` Michael Eager
2026-06-02  5:05       ` [PATCH v2] " Gopi Kumar Bulusu
2026-06-11  0:39         ` Michael Eager
2026-06-11  1:19           ` Gopi Kumar Bulusu
2026-06-11  1:41             ` Simon Marchi
2026-06-11  1:44               ` Gopi Kumar Bulusu
2026-06-11 12:52             ` Michael Eager

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=CAL1P33ys5M-dsBDJ5U1tnUXkbhLTeZT46KOad8vMgJ+M+MbWDg@mail.gmail.com \
    --to=gopi@sankhya.com \
    --cc=binutils@sourceware.org \
    --cc=eager@eagercon.com \
    --cc=gdb-patches@sourceware.org \
    /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