Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: gdb@sourceware.org
Subject: seeking open source examples of GDB scripting
Date: Sun, 18 Jan 2026 20:01:23 +0100	[thread overview]
Message-ID: <631f016aca22712c52b3718cb2cd43c496a3e9f7.camel@starynkevitch.net> (raw)

Hello all,

I am seeking open source examples (or tutorials, given that I am unfamiliar with Python) of GDB scripting.

Since I have a naughty bug : https://github.com/RefPerSys/RefPerSys/issues/30

The scripting could be in GNU guile (I much prefer that language).

For example, I would like to automatically add a breakpoint to every line calling the RPS_POSSIBLE_BREAKPOINT() macro
That macro is nearly a no-op one defined in https://github.com/RefPerSys/RefPerSys/blob/19f01d3783c9f727980f21fc2c66db4837745b61/refpersys.hh#L1335

Thanks for your help.

Regards

PS. RefPerSys is a GPL licensed inference engine, I dream of it becoming a GNU project but don't know how to do that.
In the past I did contribute to GCC, https://arxiv.org/abs/1109.0779
-- 

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-18 19:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 19:01 Basile Starynkevitch [this message]
2026-01-26 16:52 ` Simon Marchi 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=631f016aca22712c52b3718cb2cd43c496a3e9f7.camel@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=gdb@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