From: "Dhananjay R. Deshpande" <dhananjayd@KPITCummins.com>
To: "Michael Snyder" <msnyder@redhat.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: RE: [PATCH] Fix problem with sim_load (h8300)
Date: Thu, 18 Dec 2003 05:50:00 -0000 [thread overview]
Message-ID: <69595093233BB547BB70CF5E492B63F203402D22@sohm.kpit.com> (raw)
Hi Michael,
For convenience I use h8300-elf-gdb built with --enable-tragets=h8300-coff. This way I can debug/test both coff and elf objects. Because of this bfd recognizes "coff-h8300" format although binary is in elf32-h8300 format and it worked for me.
The patch works fine for elf only build. Please check it in.
Regards,
Dhananjay
> -----Original Message-----
> From: Michael Snyder [mailto:msnyder@redhat.com]
> Sent: Thursday, December 18, 2003 1:25 AM
> To: Dhananjay R. Deshpande
> Cc: gdb-patches@sources.redhat.com
> Subject: [PATCH] Fix problem with sim_load (h8300)
>
>
>
> Dhananjay, this seems to fix the problem. I discovered that
> in most cases people don't pass a specific bfd-target to bfd_openr.
> They just let bfd figure out which target to use.
>
> I'll give you a chance to try this out before I check it in.
>
> Michael
>
>
next reply other threads:[~2003-12-18 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 5:50 Dhananjay R. Deshpande [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-24 9:23 Dhananjay R. Deshpande
2004-01-06 0:59 ` Michael Snyder
2003-12-17 5:59 H8300 Patch - Fix GDB crash problem when object file of different H8 cpu is loaded Dhananjay R. Deshpande
2003-12-17 19:32 ` Michael Snyder
2003-12-17 19:54 ` [PATCH] Fix problem with sim_load (h8300) Michael Snyder
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=69595093233BB547BB70CF5E492B63F203402D22@sohm.kpit.com \
--to=dhananjayd@kpitcummins.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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