From: "Kris Warkentin" <kewarken@qnx.com>
To: <gdb@sources.redhat.com>
Subject: auto-solib-add when attaching to inferior
Date: Wed, 16 Apr 2003 18:59:00 -0000 [thread overview]
Message-ID: <020001c3044b$31fba6e0$2a00a8c0@dash> (raw)
When I run a remote process using our QNX remote protocol, I get a solib
breakpoint set properly and from then on, if solibs are loaded, their
symbols automatically get added (auto-solib-add is on by default). If,
however, I attach to the process, even if auto-solib-add is on, I still have
to go 'shared' to get them to load. If I 'maint info breakpoints' on the
attached process, I see that there isn't a shlib-events breakpoint set on
the attached process so I assume either enable_break() isn't getting called
or is failing.
I'm still building my debug gdb to test but I'm hoping someone will tell me,
"Oh, when you attach you should always call such-and-such function" and I
can just add it to our back end code.
cheers,
Kris
next reply other threads:[~2003-04-16 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 18:59 Kris Warkentin [this message]
2003-04-16 19:04 ` Daniel Jacobowitz
2003-04-16 22:05 ` Kris Warkentin
2003-04-16 22:14 ` Daniel Jacobowitz
2003-04-17 14:12 ` Kris Warkentin
2003-04-17 18:14 ` Kris Warkentin
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='020001c3044b$31fba6e0$2a00a8c0@dash' \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.com \
/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