Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, lgustavo@codesourcery.com
Subject: Re: [PATCH, gdbsim] Avoid silly crash when no binary is loaded
Date: Thu, 20 Jun 2013 18:34:00 -0000	[thread overview]
Message-ID: <51C34475.4090301@redhat.com> (raw)
In-Reply-To: <201306201350.31839.vapier@gentoo.org>

On 06/20/2013 06:50 PM, Mike Frysinger wrote:

> well, there's a bit more nuance than that.  consider the operating environment 
> (literally, --environment operating).  when you connect to that, it's like you 
> took jtag and connected it to a cpu fresh out of reset.  sure, there's no 
> "program" loaded in its memory, but there's still plenty you can do to the 
> device like poke memory and see how it reacts -- whether it be external SDRAM, 
> or a parallel flash, or on-chip L1/L2, or memory mapped registers for the 
> peripherals, or an async memory bus, or an on-chip boot/ROM (which has both 
> code & data).  maybe i'm an odd ball, but i find this scenario great for both 
> testing, development (like writing new sim device models), and one-off checks.  
> the fact that i need to compile & link a dummy program just to load it into 
> the sim so i can start poking around is obnoxious.  similarly, when i have 
> just a .bin of raw code/data (e.g. `objcopy -O binary foo.elf foo.bin` which 
> is common in the embedded world), how am i going to get that into the 
> simulator ?  when i'm connected to jtag, i could use "load" & friends to copy 
> it to memory, set the pc, and let it run.  with the sim, i need to create a 
> dummy .s that does .incbin "foo.bin" and compile+link that.

This makes a lot of sense to me.  I fully agree.

Thanks,
-- 
Pedro Alves


  reply	other threads:[~2013-06-20 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 21:09 Luis Machado
2013-06-19 11:43 ` Pedro Alves
2013-06-19 12:20   ` Luis Machado
2013-06-19 14:53     ` Pedro Alves
2013-06-19 15:20       ` Luis Machado
2013-06-20 13:39         ` Luis Machado
2013-06-20 17:50     ` Mike Frysinger
2013-06-20 18:34       ` Pedro Alves [this message]
2013-06-20 21:33       ` Stan Shebs
2013-06-20 22:00         ` Mike Frysinger
2013-06-21 10:58           ` 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=51C34475.4090301@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=vapier@gentoo.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