From: Eli Zaretskii <eliz@gnu.org>
To: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v8] gdb: Add source-tracking breakpoints feature
Date: Fri, 07 Aug 2026 14:14:18 +0300 [thread overview]
Message-ID: <86se4q41yt.fsf@gnu.org> (raw)
In-Reply-To: <CAJVr-ENHVQYhOtuSMYpJ5vtKN4711KeJd0ssAQ3WY_xgJP6+YA@mail.gmail.com> (message from Alexandra Petlanova Hajkova on Fri, 7 Aug 2026 10:42:49 +0200)
> From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
> Date: Fri, 7 Aug 2026 10:42:49 +0200
> Cc: gdb-patches@sourceware.org
>
> Hi Eli,
>
> This feature works in all GDB builds, it only requires that source files are accessible and the
> binary was compiled with debug info (line numbers). No special dependencies like `compile`
> are needed.
OK, that's good to know. Please consider mentioning these
preconditions in the manual.
> The maintenance command will be added to NEWS in the next version, thanks for catching that.
Great, thanks.
next prev parent reply other threads:[~2026-08-07 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 9:40 Alexandra Hájková
2026-07-14 11:23 ` Andrew Burgess
2026-07-14 12:22 ` Eli Zaretskii
2026-08-07 8:42 ` Alexandra Petlanova Hajkova
2026-08-07 11:14 ` Eli Zaretskii [this message]
2026-07-18 3:31 ` Kevin Buettner
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=86se4q41yt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ahajkova@redhat.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