From: "vamsi krishna" <vamsi.krishnak@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: [FIXED] Question about the segment [[ 60000fff80000000-60000fff80004000 rw-p 0000000000000000 00:00
Date: Fri, 09 Jun 2006 06:59:54 +0000 [thread overview]
Message-ID: <3faf05680606082359m32cea491m396df061c3797ff2@mail.gmail.com> (raw)
Hello All,
Thank you for all your comments, I fixed my issue on linuxipf. The
problem is a standard memory corruption problem. I had a 'FILE *ptr'
which was opened in the save run, during the restore run since the
FILE *'s are not restored I reopen the FILE * and do a memcpy into
*ptr since in the restore run *ptr is not a valid memory this caused
the corruption and _IO_flush_all was stuck.
Thank you once again.
Best,
Vamsi
reply other threads:[~2006-06-09 6:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3faf05680606082359m32cea491m396df061c3797ff2@mail.gmail.com \
--to=vamsi.krishnak@gmail.com \
--cc=linux-ia64@vger.kernel.org \
/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