From: "Le Lain, Olivier" <olivier.lelain@xrce.xerox.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.12 and gcore
Date: Tue, 11 Oct 2005 15:21:39 +0200 [thread overview]
Message-ID: <434BBC63.6040800@xrce.xerox.com> (raw)
Hello,
First, sorry if it's not the right place but after having googling for
days, I didn't succed in finding some infos.
Since the kernel 2.6.12 (at least every 2.6.12 from Fedora Core 3) , I'm
unable to generate useful core dumps with gcore.
I always have the following messages :
warning: The current VSYSCALL page code requires an existing execuitable.
Use "add-symbol-file-from-memory" to load the VSYSCALL page by hand
Then ,indeed, there no more symbols included in my core files, which
makes them useless.
Is this a security issue ? (selinux is disabled) , a gdb one ? (gdb
hasn't been updated since quite a long time )
Does someone know if there's an issue for that (a lot of my admin
scripts rely on gcore so this is really annoying)
I havn't this problem with 2.6.11 kernels but 2.6.12 solved a lot of
other bugs so I'd rather use it.
Thanks.
--
Cordialement / Cheers.
-Olivier
CNS
reply other threads:[~2005-10-11 13:21 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=434BBC63.6040800@xrce.xerox.com \
--to=olivier.lelain@xrce.xerox.com \
--cc=linux-kernel@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