From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: What about check the bfd_arch_info before load the solib?
Date: Wed, 01 Jul 2009 06:55:00 -0000 [thread overview]
Message-ID: <daef60380906302355s9648e19n846821ed8c878e75@mail.gmail.com> (raw)
In-Reply-To: <4A4AE147.5060800@vmware.com>
On Wed, Jul 1, 2009 at 12:08, Michael Snyder<msnyder@vmware.com> wrote:
> Hui Zhu wrote:
>>
>> Hi guys,
>>
>> 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.
>>
>> I think maybe we can add some check code to check if the bfd_arch_info
>> of this solib is same with the current_gdbarch before load this solib
>> in.
>> If not same, output a warning to let user set gdb to load right lib.
>>
>> What do you think about it?
>
> It would certainly be reasonable to reject an object file (eg. shlib)
> if it has the wrong architecture type. I'm surprised that we don't
> already do it.
Me too. I will try to make a patch for it.
Thanks,
Hui
prev parent reply other threads:[~2009-07-01 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 13:07 Hui Zhu
2009-07-01 4:11 ` Michael Snyder
2009-07-01 6:55 ` Hui Zhu [this message]
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=daef60380906302355s9648e19n846821ed8c878e75@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@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