public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: 好 <swdtian@163.com>, gdb@sourceware.org
Subject: Re: Is there any information about gpu debugging?
Date: Tue, 5 Jul 2022 20:03:44 -0400	[thread overview]
Message-ID: <6ed0cfa1-a3bb-f7bc-54d0-bb2abb6b11d4@polymtl.ca> (raw)
In-Reply-To: <62b767e7.d30.181cbe55427.Coremail.swdtian@163.com>

On 2022-07-04 21:06, 好 via Gdb wrote:
> Hi, Is this the channel for raising questions?

Hi, yes.

> I have been very interested in gdb recently. I want to develop a set
> of gdb that supports GPU debugging, but I don't know where to start.

What do you mean by "a set of gdb"?

> Do you have any good suggestions? What is the difference between AMD's
> ROCGDB and NVIDIA's cuda-gdb and GDB? Is there any information?

Cuda-gdb and ROCgdb are two separate forks of GDB, made to debug Cuda
and ROCm programs respectively.  They are not interchangeable, as they
are both designed to debug programs running on their respective
platforms.  They currently both reside outside of the upstream GDB tree.
I can't speak for Nvidia, but AMD intends on (and is actively working
on) contributing ROCgdb to upstream gdb.  So in some not too distant
future, it should be possible to debug ROCm programs with an upstream
GDB build.

I am not sure what kind of differences between the two you are after, so
feel free to ask further questions.

Simon

      reply	other threads:[~2022-07-06  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05  1:06 
2022-07-06  0:03 ` Simon Marchi [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=6ed0cfa1-a3bb-f7bc-54d0-bb2abb6b11d4@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb@sourceware.org \
    --cc=swdtian@163.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).