NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/unix/wizards/5265

Internet Message Format | 1992-12-18 | 1.7 KB

Xref: sparky comp.unix.wizards:5265 comp.unix.programmer:5728 comp.unix.questions:14789
Newsgroups: comp.unix.wizards,comp.unix.programmer,comp.unix.questions
Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!geraldo.cc.utexas.edu!slcs.slb.com!leo.asc.slb.com!sjsca4!bharat
From: [e-mail] (Bharat Venkatasubramanian)
Subject: Portability issues in using a memory dump
Message-ID: <[e-mail]>
Originator: bharat@surya
Organization: Schlumberger Technologies, San Jose, CA
Date: Thu, 17 Dec 92 22:24:02 GMT
Lines: 27


Folks!

I have a wierd problem.  I would like to dump the contents of a chunk of
contiguous memory locations.   The contents represent some complex graph
structure which once built is constant over different invocations of the
program.

Instead of traversing the graph and dumping its contents, I would like to
dump the contents of this contiguous memory.  Subsequent invocations of
this program could then use mmap() system call to map the information in
this file to the address used when the file was first created.  This would
also preserve the pointer addresses since I am using the same address
space that was used during the creation of this memory dump.  The program
has static behavior until the creation of this graph and so on the same
machine I will definitely be able to guarantee the availability of that
address space.  One of my concerns is will the address space be different
on different Operating Systems??

If any of you folks have tried something like this before, I would appreciate
it if you could share the problems/pitfalls with this solution.

Please email any suggestions to [e-mail]

Thanks in advance.

Bharat