From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rajinikanth.p@gmail.com>
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com
 [IPv6:2a00:1450:4864:20::136])
 by sourceware.org (Postfix) with ESMTPS id 507993858D29
 for <gdb@sourceware.org>; Sat, 26 Dec 2020 06:48:54 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 507993858D29
Received: by mail-lf1-x136.google.com with SMTP id l11so13174794lfg.0
 for <gdb@sourceware.org>; Fri, 25 Dec 2020 22:48:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=WpWme+Pv2dAsX+m30/1YiG0tdOZuMQ7/Fp61/gkCwU4=;
 b=XBFZfLKQ8dzm7s6+OvahZ3gyheubrl16uNv6o6uMrE0CbOZIDuY2UhhQeuDa6gDvig
 JsabzCRBx0hmBLEXux2HmsMyCfvmw38kX7XCwvbMSAgvq+FL4wU4TlRZd1FkOFN0Vp8N
 Qmm4ufksuV7ztBI3r2A1W7PZJ5qVYP2ow8gn8Fs55gksr4/TF/qsCk0KgRQMXimWYgUe
 KvrURZjJluXwAc++thY52iEoWfBgDXEZwYP68+0X06sYH4nsVSDb96tzKg7zLcAOhN2y
 S/7lfZKQh95xZm9t84vRTIxH9YKyE/25FhLFq9oFQhRg0OzZATGkRBgiee0sBqINFzXW
 Ec2A==
X-Gm-Message-State: AOAM533ARA6UFbfzThQ621Q3RQ79FQg1zWXOr33JcrdKmQcpnDp8mshL
 hYS0l2YSQLN4Aes6r6CWFMy4c4rha7JG9+CmdkaZYvpff30nzg==
X-Google-Smtp-Source: ABdhPJyEHUc8Dl8eUhDtIyS6UnK6hHkfmRqJMz/uHteeRW7GSta8OQPIMhx1GLlMx58MmH7aQ8XVOIV6kTUCuUUwAi0=
X-Received: by 2002:a2e:9d85:: with SMTP id c5mr17142156ljj.80.1608965332947; 
 Fri, 25 Dec 2020 22:48:52 -0800 (PST)
MIME-Version: 1.0
From: Rajinikanth Pandurangan <rajinikanth.p@gmail.com>
Date: Fri, 25 Dec 2020 22:48:41 -0800
Message-ID: <CAGsSNHDFJ7HJNt6sC3mUoy_OuU-wH8ti=ZnagFsnSzN=CdiYaA@mail.gmail.com>
Subject: GDB with PCIe device
To: gdb@sourceware.org
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE,
 RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
X-BeenThere: gdb@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb mailing list <gdb.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb>,
 <mailto:gdb-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb>,
 <mailto:gdb-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Dec 2020 06:48:55 -0000

Hello,

As per my understanding, gdb calls ptrace system calls which intern uses
kernel implementation of architecture specific action (updating debug
registers,reading context memory...) to set breakpoints, and so on.

But in case of running gdb with PCIe devices such as gpu or fpga, how does
the hardware specific actions are being done?

Should device drivers provide ptrace equivalent kernel implementation?

 Could any of the gdb gurus shed some light on debug software stacks in
debugging software that runs on one of the mentioned pcie devices?

Thanks in advance,