From: Chris Johns <chrisj@rtems.org>
To: Joel Sherrill <joel.sherrill@oarcorp.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: lm32 run vs gdb
Date: Mon, 14 Mar 2016 00:32:00 -0000 [thread overview]
Message-ID: <56E6067C.30809@rtems.org> (raw)
In-Reply-To: <20160311215546.GN6588@vapier.lan>
On 12/03/2016 08:55, Mike Frysinger wrote:
> On 11 Mar 2016 15:12, Joel Sherrill wrote:
>> I think the command line arguments for the lm32 simulator
>> are not getting parsed the same for "run" as when you do
>> "tar sim" in gdb. Executables work with gdb that don't
>> with run.
>
> wtf is "tar" ? hmm, guess it's short for "target sim" ...
>
>> lm32-rtems4.12-run --hw-file lm32_evr.conf \
>> --memory-region 0x08000000,0x4000000 ticker.exe
>>
>> In gdb, the tar sim command is:
>>
>> tar sim --hw-file lm32_evr.conf --memory-region 0x08000000,0x4000000
>>
>> lm32_evr.conf is
>>
>> /lm32cpu
>> /lm32uart/reg 0x80006000 0x100
>> /lm32uart > int int0 /lm32cpu
>> /lm32timer/reg 0x80002000 0x80
>> /lm32timer > int int1 /lm32cpu
>>
>> Any ideas what's broken or where I should look?
>
> the arg parsing codepaths are the same -- see sim/lm32/sim-if.c and
> the sim_open function. gdb & the run frontend both call that.
It looks like something has changed. With gdb-7.11 and the
sparc-rtems4.11 target I am seeing:
$ /opt/work/rtems/4.12/bin/sparc-rtems4.12-run
./sparc-rtems4.12/c/erc32/testsuites/samples/ticker/ticker.exe
SIS - SPARC instruction simulator 2.7.5, copyright Jiri Gaisler 1995
Bug-reports to jgais@wd.estec.esa.nl
sis> quit
With gdb-7.9 it use to just run the executable. GDB works.
Chris
prev parent reply other threads:[~2016-03-14 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 21:13 Joel Sherrill
2016-03-11 21:55 ` Mike Frysinger
2016-03-14 0:32 ` Chris Johns [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=56E6067C.30809@rtems.org \
--to=chrisj@rtems.org \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@oarcorp.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