All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: vamsi krishna <vamsi.krishnak@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Program to convert core file to executable.
Date: Wed, 24 May 2006 16:08:37 -0400	[thread overview]
Message-ID: <20060524200837.GA5679@nevyn.them.org> (raw)
In-Reply-To: <3faf05680605241306t64f63225i4d25af3e92a9d9f9@mail.gmail.com>

On Thu, May 25, 2006 at 01:36:08AM +0530, vamsi krishna wrote:
> o Does the other PHDRS for which FileSiz is zero correspond to the
> dynamic shared objects (.so) text ?? example in the above we see (2
> **ed ) PHDR with VirtAddr as 0xf649c000 , so this means the text of
> some shared .so has been mapped here right?

Probably.

> o I have question about the memory mapping with permissions r--s or
> r--p (gconv used by glibc gets mapped like this some time) , so does
> the core file contains this information of the memory mappings?
> 
> o Is there a way I can findout the standard which the OS follows to
> write the core file?

No.  Core files change from time to time.  David Miller recently
proposed changing these.

> o Rather than depending on the OS core file, hows your opinion on
> writing out all the mappings form /proc/<pid>/maps as PT_LOAD into a
> elf formatted file of type ET_EXEC, do you think this works? rather
> than converting core file to exe?

You might want to take a look at GDB's generate-core-file command.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-05-24 20:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 17:18 Program to convert core file to executable vamsi krishna
2006-05-24 17:25 ` vamsi krishna
2006-05-24 17:38 ` Daniel Jacobowitz
2006-05-24 20:06   ` vamsi krishna
2006-05-24 20:08     ` Daniel Jacobowitz [this message]
2006-05-24 20:19       ` vamsi krishna
2006-05-24 20:25         ` Daniel Jacobowitz
2006-05-24 20:31     ` H. Peter Anvin
2006-05-24 20:52     ` Eric Piel
2006-05-24 21:33     ` Greg KH
2006-05-25 11:04 ` Marcel Holtmann

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=20060524200837.GA5679@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vamsi.krishnak@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.