* mem command and set command
@ 2008-03-07 13:56 bjgnu
2008-03-07 18:19 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: bjgnu @ 2008-03-07 13:56 UTC (permalink / raw)
To: gdb
hello all,
Executing the following GDB commands:
mem 0x0 0x100 16
set *0x0=0x12345678
I found the 3rd parameter of write_memory (CORE_ADDR memaddr, const
bfd_byte *myaddr, int len) is always 4.
I think the length should be 2 because "mem 0x0 0x100 16" has set memory
width to 16.
Does "mem" command affect write memory operation?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: mem command and set command
2008-03-07 13:56 mem command and set command bjgnu
@ 2008-03-07 18:19 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2008-03-07 18:19 UTC (permalink / raw)
To: bjgnu; +Cc: gdb
On Fri, Mar 07, 2008 at 04:55:53PM +0800, bjgnu@sunnorth.com.cn wrote:
> hello all,
>
> Executing the following GDB commands:
>
> mem 0x0 0x100 16
> set *0x0=0x12345678
>
> I found the 3rd parameter of write_memory (CORE_ADDR memaddr, const
> bfd_byte *myaddr, int len) is always 4.
> I think the length should be 2 because "mem 0x0 0x100 16" has set memory
> width to 16.
> Does "mem" command affect write memory operation?
No. The width appears to be unused. I just use set {short} 0 =
0x1234 when I want to generate a 16-bit write.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-03-07 13:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-07 13:56 mem command and set command bjgnu
2008-03-07 18:19 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox