From: Adrian Sendroiu <adrian.sendroiu@freescale.com>
To: <gdb-patches@sourceware.org>, <palves@redhat.com>
Subject: Re: [PATCH] call observer_notify_new_objfile after the attach command
Date: Thu, 10 Jul 2014 10:57:00 -0000 [thread overview]
Message-ID: <1404989787-18250-1-git-send-email-adrian.sendroiu@freescale.com> (raw)
In-Reply-To: <53BD4F45.4090000@redhat.com>
Thanks, I added a call to remote_check_symbols in the post_attach hook.
Adrian
From 0820f5ab475bd9e261e7be26dabbd30e5df60544 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Adrian=20=C8=98endroiu?= <adrian.sendroiu@freescale.com>
Date: Thu, 10 Jul 2014 11:16:41 +0300
Subject: [PATCH] call remote_check_symbols after attaching
---
gdb/remote.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/gdb/remote.c b/gdb/remote.c
index 3aa030c..8b438c7 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -4484,6 +4484,13 @@ extended_remote_attach (struct target_ops *ops, const char *args, int from_tty)
extended_remote_attach_1 (ops, args, from_tty);
}
+static void
+extended_remote_post_attach (struct target_ops *ops, int pid)
+{
+ if (symfile_objfile)
+ remote_check_symbols();
+}
+
\f
/* Check for the availability of vCont. This function should also check
the response. */
@@ -11530,6 +11537,7 @@ Specify the serial device it is connected to (e.g. /dev/ttya).";
extended_remote_ops.to_mourn_inferior = extended_remote_mourn;
extended_remote_ops.to_detach = extended_remote_detach;
extended_remote_ops.to_attach = extended_remote_attach;
+ extended_remote_ops.to_post_attach = extended_remote_post_attach;
extended_remote_ops.to_kill = extended_remote_kill;
extended_remote_ops.to_supports_disable_randomization
= extended_remote_supports_disable_randomization;
--
1.7.9.5
next prev parent reply other threads:[~2014-07-10 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 13:51 Adrian Sendroiu
2014-07-09 14:18 ` Pedro Alves
2014-07-10 10:57 ` Adrian Sendroiu [this message]
2014-07-10 13:53 ` Pedro Alves
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=1404989787-18250-1-git-send-email-adrian.sendroiu@freescale.com \
--to=adrian.sendroiu@freescale.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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