From: "Frank Ch. Eigler" <fche@redhat.com>
To: Manganotto Filippo <in000566@students.univr.it>
Cc: gdb@sources.redhat.com
Subject: Re: Connect 2 mips simulator
Date: Fri, 07 Sep 2001 07:09:00 -0000 [thread overview]
Message-ID: <20010907100901.A19650@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109071359470.29146-100000@delta046.sci.univr.it>
Hi -
: I create file pippo.txt with command that you tell me and then I
: run simulator with parameters and the programma Hello World, but into file
: it doesn't write nothing.
As the --help documentation suggests, the --memory-mapfile command
applies to the following --memory-region to be modelled by the simulator.
So,
FOO-run --memory-mapfile blah.txt --memory-region 0x2000000,0x8000
will make available to the target program an extra memory region
0x02000000-0x02007FFF. Any reads/writes to that region of memory
will be visible in the appropriate part of the file. (The exact
time at which the memory and the file are synchronized is not
specified. If you map the same file into two simulators on the
same host, you'll generally see instant synchronization.)
: If I have understood just, into file I would have to find the simulator
: memory into file, such as for example:
: <memory location> : <memory value>
: Is this right?
Your target program would have to read/write those specific areas of
memory. For example:
#define MMAPBASE 0x02000000
#define MMAPBYTE ((volatile unsigned char *) MMAPBASE)
strcpy (& MMAPBYTE[0], "hello world\n");
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7mNT9VZbdDOm/ZT0RAhiBAJ9ObcfdRosSr84HNkuB3ai4gtafawCdFOgD
jQjTwDfqG5pAqaleQVSt58E=
=aKFI
-----END PGP SIGNATURE-----
From tcombs@urbana.css.mot.com Fri Sep 07 09:10:00 2001
From: Tim Combs <tcombs@urbana.css.mot.com>
To: gdb@sourceware.cygnus.com
Subject: Memory and gdb
Date: Fri, 07 Sep 2001 09:10:00 -0000
Message-id: <20010907111048.C24826@urbana.css.mot.com>
X-SW-Source: 2001-09/msg00061.html
Content-length: 415
I have memory management questions. I thought the way to allocate
memory in gdb was with xmalloc and to free it was xfree. (At least
that's what the internals document says). But when I grep through
the source, I can find xmalloc but no xfree. When I try to link
I get xfree multiply defined. It seems to be found in readline and
in utils.c. What's the proper way to free memory?
Tim
Tim.Combs@motorola.com
next prev parent reply other threads:[~2001-09-07 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 4:37 Manganotto Filippo
2001-09-07 4:42 ` Frank Ch. Eigler
[not found] ` <Pine.LNX.4.33.0109071359470.29146-100000@delta046.sci.univr.it>
2001-09-07 7:09 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-06 15:19 Frank Ch. Eigler
2001-09-03 8:42 Zampieri Marco
2001-09-03 9:19 ` Frank Ch. Eigler
2001-09-06 5:44 ` Zampieri Marco
2001-09-06 6:46 ` Frank Ch. Eigler
2001-09-06 7:46 ` Zampieri Marco
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=20010907100901.A19650@redhat.com \
--to=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=in000566@students.univr.it \
/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