Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: gdb@sourceware.org
Cc: team@refpersys.org
Subject: GDB variants accepting plugins (to the debugger) ?
Date: Fri, 30 Jan 2026 14:13:51 +0100	[thread overview]
Message-ID: <06d90d0ef774cf4ffd69a675a9092afee18a3446.camel@starynkevitch.net> (raw)

Hello

I am using GDB-17.1 on Linux/Debian/x86-64 to debug a C++ coded, GPL licensed, inference engine


Is there any GDB variant accepting plugins to the debugger process
(these could be definitely useful to display C++ data in a nice way, std::vector or std::map instances come to mind immediately).

I do know that GDB accept eg Guile or Python scripts.
But coding manually a Python or Guile function for every important C++ classes of a software is very time consuming


I regret that GDB 17.1 has not evolved into something similar to the old and unmaintained UPS open source debugger
https://ups.sourceforge.net/ which sadly is not working on Linux/AMD-64 computers running a recent kernel 6.17 and
and using recent libc and libstdc++

Regards.
-- 

Basile STARYNKEVITCH                    basile AT starynkevitch DOT net
8 rue de la Faïencerie                       http://starynkevitch.net/Basile/  
92340 Bourg-la-Reine                         https://github.com/bstarynk
France                                https://github.com/RefPerSys/RefPerSys
                  https://orcid.org/0000-0003-0908-5250

             reply	other threads:[~2026-01-30 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 13:13 Basile Starynkevitch [this message]
2026-01-30 13:33 ` Eli Zaretskii via Gdb
2026-01-30 15:35   ` Simon Marchi via Gdb
2026-01-30 17:03     ` Basile Starynkevitch
2026-01-30 17:16       ` Simon Marchi via Gdb
2026-01-30 20:12 ` Tom Tromey
2026-01-31  2:36   ` Matt Rice via Gdb
2026-01-31 17:00     ` Tom Tromey
2026-02-02 13:49       ` Jan Vrany via Gdb

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=06d90d0ef774cf4ffd69a675a9092afee18a3446.camel@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=gdb@sourceware.org \
    --cc=team@refpersys.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