From: K <cq.personal@gmail.com>
To: gdb <gdb@sourceware.org>
Subject: Problem sending program a signal on hitting breakpoint - an anomaly?
Date: Fri, 28 Jul 2023 16:50:50 +0200 [thread overview]
Message-ID: <CACTzTFBuSp_pNbXYp2_qNbRB0byFRtcRTYWtVJr=ve1JfyNOTQ@mail.gmail.com> (raw)
In-Reply-To: <CACTzTFA8v9Miaw01oXF4xoazyBavh94p+i2aqVP4vo1gPFrRLg@mail.gmail.com>
vaxx-induced prions eating my brain!
inserting command
ignore $bpnum 1
does the trick.
replacement question: early in my gdb endeavours I tried to use libgdb.a
but got discouraged by the entanglement with other libraries it needed
linking with
such as libreadline.a.
is there any plan to make a single library available, static or dynamic?
thanks in advance.
next prev parent reply other threads:[~2023-07-28 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:11 K
2023-07-28 14:50 ` K [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-28 8:47 K
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='CACTzTFBuSp_pNbXYp2_qNbRB0byFRtcRTYWtVJr=ve1JfyNOTQ@mail.gmail.com' \
--to=cq.personal@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).