This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: lm32 run vs gdb

From: Mike Frysinger <vapier at gentoo dot org>
To: Joel Sherrill <joel dot sherrill at oarcorp dot com>
Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>, Chris Johns <chrisj at rtems dot org>
Date: Fri, 11 Mar 2016 16:55:46 -0500
Subject: Re: lm32 run vs gdb
Authentication-results: sourceware.org; auth=none
References: <56E334D4 dot 4010908 at oarcorp dot com>

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

Attachment: signature.asc
Description: Digital signature

Follow-Ups:
- Re: lm32 run vs gdb
  - From: Chris Johns

References:
- lm32 run vs gdb
  - From: Joel Sherrill

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]