Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Cc: Michael Snyder <msnyder@vmware.com>
Subject: [RFA] Check solib bfd arch
Date: Fri, 03 Jul 2009 09:52:00 -0000	[thread overview]
Message-ID: <daef60380907030252j849c5f3g475cbdce6fb13c33@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Hi,

In cross-compile remote debug environment, the gdb will load the solib
of local host if user doesn't set sysroot or something.
Load the wrong lib will make gdb get error.

So I make a patch check the solib bfd arch after load it.  I am not
check the other thing in arch_info because the mach of solib and
inferior is not same (powerpc) sometime.

This patch is tested in a i386 ubuntu and powerpc linux.

Thanks,
Hui

2009-07-03  Hui Zhu  <teawater@gmail.com>

	* solib.c (solib_bfd_open): Check solib bfd arch.

---
 solib.c |    8 ++++++++
 1 file changed, 8 insertions(+)

--- a/solib.c
+++ b/solib.c
@@ -311,6 +311,14 @@ solib_bfd_open (char *pathname)
 	     found_pathname, bfd_errmsg (bfd_get_error ()));
     }

+  /* Check bfd arch.  */
+  if (bfd_get_arch (abfd) != gdbarch_bfd_arch_info (target_gdbarch)->arch)
+    {
+      bfd_close (abfd);
+      make_cleanup (xfree, found_pathname);
+      error (_("`%s': ARCH not same with inferior."), found_pathname);
+    }
+
   return abfd;
 }

[-- Attachment #2: solib-check-bfd_arch_info.txt --]
[-- Type: text/plain, Size: 489 bytes --]

---
 solib.c |    8 ++++++++
 1 file changed, 8 insertions(+)

--- a/solib.c
+++ b/solib.c
@@ -311,6 +311,14 @@ solib_bfd_open (char *pathname)
 	     found_pathname, bfd_errmsg (bfd_get_error ()));
     }
 
+  /* Check bfd arch.  */
+  if (bfd_get_arch (abfd) != gdbarch_bfd_arch_info (target_gdbarch)->arch)
+    {
+      bfd_close (abfd);
+      make_cleanup (xfree, found_pathname);
+      error (_("`%s': ARCH not same with inferior."), found_pathname);
+    }
+
   return abfd;
 }
 

             reply	other threads:[~2009-07-03  9:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  9:52 Hui Zhu [this message]
2009-07-05 21:36 ` Ulrich Weigand
2009-07-06  3:03   ` Hui Zhu
2009-07-07 16:45     ` Ulrich Weigand
2009-07-08  2:46       ` Hui Zhu
2009-07-09 13:43         ` Ulrich Weigand
2009-07-09 16:50           ` Hui Zhu
2009-09-17 22:56         ` Joel Brobecker
2009-09-18  5:05           ` Hui Zhu
2009-09-18 12:50           ` Ulrich Weigand
2009-09-18 13:06             ` Ulrich Weigand
2009-09-18 13:10             ` Daniel Jacobowitz
2009-09-18 14:24               ` Joel Brobecker
2009-09-18 14:08             ` Mark Kettenis
2009-09-18 14:11               ` Mark Kettenis
2009-09-18 14:39               ` Daniel Jacobowitz
2009-09-18 14:53                 ` Pedro Alves
2009-09-18 16:14                   ` Ulrich Weigand
2009-09-18 16:25                     ` Daniel Jacobowitz
2009-09-18 16:41                       ` Pedro Alves
2009-09-18 16:44                         ` Daniel Jacobowitz
2009-09-18 16:45                         ` Pedro Alves
2009-09-18 17:17                           ` Joel Brobecker
2009-09-18 20:43                             ` Joel Brobecker
2009-09-22 23:04           ` Joel Brobecker

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=daef60380907030252j849c5f3g475cbdce6fb13c33@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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