Re: lm32 run vs gdb

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.
-mike

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJW4z7iAAoJEEFjO5/oN/WB8BoP/112oQ6jwOKirl4FaFW3d35o
2xdl7XCXp2rN/DVU/IKwdSzxBwue0k7MZTrymyDTfKzRYmLs9FP/XBbKscRp1Sm2
/yisrFCoG0z2Uqj3/j/UGyVoItnYeeqq0PR9etKhV/1+zpuw9yYbkYcY3anRlCvG
CDivPjdEwlJABN/2Z2wFgONkCPDQDVZTGQmfkV6QLL4Plkz8Vro7pGL3rAAaXXM6
4MEZ54A27NVkEIj3VsydFZp79eJaTXCrlRBbzio1yQGqmy46PSxMffBiJxVlqSGh
YLH9YwnOPpoAIarkMrj44gLWXa24KvtHfcLOCgdxDI4TPOdms5Wg9sq/xRr8oBUM
323TedQu93lQ1w5JACiG5gau1H+7D9db6hs+VIDhB5Xf5c5XgWZBxWkvtw6Ee2Xy
wvfvsYSmktgIiv6bNGl5poV6ASQk4ROaf8R4BDfv5msjfYUjDk1tfesLvQSWQyrX
pbDnb0HIb5reZzzampNvNBS5ZhptTX3zDa6EUPpHdA4l1fwKhZj9+yn9g1ZCrvV5
bfQg+a77aiN2Aw2r8GWaiPMoS8dpN09ZZxGeCjpljmMMafVd1ngUA35VTZl4B6LH
9a4y0KQ7IlByluYp+Vx6g2yEz7NsSq8M5pgmDNJsgksARrlGtdMNQshxVhpKVw1M
0ibRMLdnR5iG9KC1m7rG
=MzHx
-----END PGP SIGNATURE-----