Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] generating the map file
Date: Wed, 29 Jan 2014 09:39:38 +0100 (CET)	[thread overview]
Message-ID: <371927488.4844376.1390984778154.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <OF622178ED.DD9A35DB-ON85257C62.00673408-85257C62.006749F5@LocalDomain>

As far as I understand, map files (or memory map files) are a 
representation of the memory space of a single application

It makes sense to have a "complete memory map" when you have 
a single application running on your system (typically a microcontroler)

when you have a machine with a MMU i'm not sure it makes much 
sense... you can have a memory map for the kernel, a memory map for each
application, but i'm not sure what a memory map for the complete
buildroot build would be...

maybe if you use an initrd and have your whole FS in ram ? but even in
that case i'm not convinced that makes sense...

Cordialement 

J?r?my Rosen 
+33 (0)1 42 68 28 04

fight key loggers : write some perl using vim 


Open Wide Ingenierie

23, rue Daviel
75013 Paris - France
www.openwide.fr





----- Mail original -----
> 
> Hi,
> 
> Can someone provide inputs on how to generate the .map file for the
> entire build (from buildroot).
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

      parent reply	other threads:[~2014-01-29  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 18:48 [Buildroot] generating the map file Naitik Amin
2014-01-29  8:21 ` Thomas Petazzoni
2014-01-29  8:39 ` Jeremy Rosen [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=371927488.4844376.1390984778154.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --cc=buildroot@busybox.net \
    /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