From: Gary Benson <gbenson@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/7] Introduce exec_file_locate_attach
Date: Wed, 01 Apr 2015 11:22:00 -0000 [thread overview]
Message-ID: <1427887341-31819-2-git-send-email-gbenson@redhat.com> (raw)
In-Reply-To: <1427887341-31819-1-git-send-email-gbenson@redhat.com>
This commit adds a new function, exec_file_locate_attach, which works
like exec_file_attach except that, instead of a filename argument, it
takes an integer process ID and attempts to determine the executable
filename from that.
gdb/ChangeLog:
* gdbcore.h (exec_file_locate_attach): New declaration.
* exec.c (exec_file_locate_attach): New function, factored
out from...
* infcmd.c (attach_command_post_wait): ...here.
---
gdb/ChangeLog | 7 +++++++
gdb/exec.c | 31 +++++++++++++++++++++++++++++++
gdb/gdbcore.h | 7 +++++++
gdb/infcmd.c | 25 ++-----------------------
4 files changed, 47 insertions(+), 23 deletions(-)
diff --git a/gdb/exec.c b/gdb/exec.c
index 113e869..ab7fcbb 100644
--- a/gdb/exec.c
+++ b/gdb/exec.c
@@ -134,6 +134,37 @@ exec_file_clear (int from_tty)
printf_unfiltered (_("No executable file now.\n"));
}
+/* See gdbcore.h. */
+
+void
+exec_file_locate_attach (int pid, int from_tty)
+{
+ char *exec_file, *full_exec_path = NULL;
+
+ /* Do nothing if we already have an executable filename. */
+ exec_file = (char *) get_exec_file (0);
+ if (exec_file != NULL)
+ return;
+
+ /* Try to determine a filename from the process itself. */
+ exec_file = target_pid_to_exec_file (pid);
+ if (exec_file == NULL)
+ return;
+
+ /* It's possible we don't have a full path, but rather just a
+ filename. Some targets, such as HP-UX, don't provide the
+ full path, sigh.
+
+ Attempt to qualify the filename against the source path.
+ (If that fails, we'll just fall back on the original
+ filename. Not much more we can do...) */
+ if (!source_full_path_of (exec_file, &full_exec_path))
+ full_exec_path = xstrdup (exec_file);
+
+ exec_file_attach (full_exec_path, from_tty);
+ symbol_file_add_main (full_exec_path, from_tty);
+}
+
/* Set FILENAME as the new exec file.
This function is intended to be behave essentially the same
diff --git a/gdb/gdbcore.h b/gdb/gdbcore.h
index 63a75f0..a437c8a 100644
--- a/gdb/gdbcore.h
+++ b/gdb/gdbcore.h
@@ -150,6 +150,13 @@ extern void core_file_command (char *filename, int from_tty);
extern void exec_file_attach (const char *filename, int from_tty);
+/* If the filename of the main executable is unknown, attempt to
+ determine it. If a filename is determined, proceed as though
+ it was just specified with the "file" command. Do nothing if
+ the filename of the main executable is already known. */
+
+extern void exec_file_locate_attach (int pid, int from_tty);
+
extern void exec_file_clear (int from_tty);
extern void validate_files (void);
diff --git a/gdb/infcmd.c b/gdb/infcmd.c
index 1c70675..f028d60 100644
--- a/gdb/infcmd.c
+++ b/gdb/infcmd.c
@@ -2489,8 +2489,6 @@ proceed_after_attach (int pid)
static void
attach_command_post_wait (char *args, int from_tty, int async_exec)
{
- char *exec_file;
- char *full_exec_path = NULL;
struct inferior *inferior;
inferior = current_inferior ();
@@ -2498,27 +2496,8 @@ attach_command_post_wait (char *args, int from_tty, int async_exec)
/* If no exec file is yet known, try to determine it from the
process itself. */
- exec_file = (char *) get_exec_file (0);
- if (!exec_file)
- {
- exec_file = target_pid_to_exec_file (ptid_get_pid (inferior_ptid));
- if (exec_file)
- {
- /* It's possible we don't have a full path, but rather just a
- filename. Some targets, such as HP-UX, don't provide the
- full path, sigh.
-
- Attempt to qualify the filename against the source path.
- (If that fails, we'll just fall back on the original
- filename. Not much more we can do...) */
-
- if (!source_full_path_of (exec_file, &full_exec_path))
- full_exec_path = xstrdup (exec_file);
-
- exec_file_attach (full_exec_path, from_tty);
- symbol_file_add_main (full_exec_path, from_tty);
- }
- }
+ if (get_exec_file (0) == NULL)
+ exec_file_locate_attach (ptid_get_pid (inferior_ptid), from_tty);
else
{
reopen_exec_file ();
--
1.7.1
next prev parent reply other threads:[~2015-04-01 11:22 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 11:22 [PATCH 0/7] Do not require "file" commands for remote targets Gary Benson
2015-04-01 11:22 ` [PATCH 3/7] Use gdb_sysroot for main executable on attach Gary Benson
2015-04-01 14:53 ` Eli Zaretskii
2015-04-15 12:45 ` Gary Benson
2015-04-15 10:43 ` Pedro Alves
2015-04-01 11:22 ` Gary Benson [this message]
2015-04-01 11:22 ` [PATCH 2/7] Introduce exec_file_find Gary Benson
2015-04-01 11:27 ` [PATCH 4/7] Introduce linux_pid_to_exec_file Gary Benson
2015-04-06 16:41 ` Doug Evans
2015-04-07 9:07 ` Gary Benson
2015-04-08 3:15 ` Doug Evans
2015-04-08 8:06 ` Gary Benson
2015-04-15 9:37 ` Pedro Alves
2015-04-15 13:14 ` [PATCH 4/7 v2] Introduce linux_proc_pid_to_exec_file Gary Benson
2015-04-15 16:01 ` Pedro Alves
2015-04-01 11:29 ` [PATCH 5/7] Implement remote_pid_to_exec_file using qXfer:exec-file:read Gary Benson
2015-04-01 14:55 ` Eli Zaretskii
2015-04-06 17:00 ` Doug Evans
2015-04-06 17:21 ` Eli Zaretskii
2015-04-06 21:57 ` Doug Evans
2015-04-07 6:09 ` Eli Zaretskii
2015-04-07 9:08 ` Gary Benson
2015-04-08 1:57 ` Doug Evans
2015-04-08 6:00 ` Eli Zaretskii
2015-04-01 11:30 ` [PATCH 6/7] Implement qXfer:exec-file:read in gdbserver Gary Benson
2015-04-06 17:11 ` Doug Evans
2015-04-07 9:19 ` Gary Benson
2015-04-17 23:43 ` Possible regression on gdb.base/attach.exp when using native-extended-gdbserver (was: Re: [PATCH 6/7] Implement qXfer:exec-file:read in gdbserver) Sergio Durigan Junior
2015-04-20 9:13 ` Gary Benson
2015-04-20 10:41 ` [OB PATCH] Fix three test failures with extended remote targets Gary Benson
2015-04-01 11:39 ` [PATCH 7/7] Access executable from remote system when first inferior appears Gary Benson
2015-04-15 10:24 ` Pedro Alves
2015-04-15 13:56 ` Gary Benson
2015-04-15 14:06 ` Gary Benson
2015-04-15 16:15 ` Pedro Alves
2015-04-15 16:09 ` Pedro Alves
2015-04-16 8:23 ` Gary Benson
2015-04-15 16:13 ` Pedro Alves
2015-04-16 9:30 ` Gary Benson
2015-04-16 9:53 ` Pedro Alves
2015-04-16 11:47 ` Gary Benson
2015-04-16 15:06 ` Eli Zaretskii
2015-04-16 15:23 ` Pedro Alves
2015-04-16 15:05 ` Eli Zaretskii
2015-04-16 19:34 ` Gary Benson
2015-04-15 16:21 ` Eli Zaretskii
2015-04-15 10:47 ` [PATCH 0/7] Do not require "file" commands for remote targets Pedro Alves
2015-04-15 12:02 ` Gary Benson
2015-04-15 12:16 ` Pedro Alves
2015-04-15 14:16 ` Gary Benson
2015-04-15 16:20 ` Pedro Alves
2015-04-17 9:01 ` Gary Benson
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=1427887341-31819-2-git-send-email-gbenson@redhat.com \
--to=gbenson@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