From: Rafal Boni <rafal.boni@eDial.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: 2.2.19pre6/7: why can't I dump core?
Date: Thu, 25 Jan 2001 18:41:32 -0500 [thread overview]
Message-ID: <200101252341.SAA01008@ninigret.metatel.office> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Folks:
Maybe I'm missing something, but nothing seems to be able to dump core
on my 2.2.19pre6 box. It looks like a lot of things look for 'current->
dumpable == 1' (actually, != 1) but I don't see the dumpable parameter
being set to 1 anywhere. Moreover, it does get set to non-zero in a
few places, but then gets reset if the binary is readable (not sure if
I read that code correctly)??
I've done a quick inspection of pre7 patch set and noticed about the
same thing. Is this an oversight, did someone intentionally turn off
core dumping until some other widget is incorporated into the patches,
or none of the above (a conspiracy, maybe? 8-).
[BTW, I'd appreciate it if you CC'ed me on any answers, as I'm not on
the list due to high traffic...]
Thanks for any insight,
- --rafal
- ----
Rafal Boni rafal.boni@eDial.com
PGP key C7D3024C, print EA49 160D F5E4 C46A 9E91 524E 11E0 7133 C7D3 024C
Need to get a hold of me? http://800.eDial.com/rafal.boni@eDial.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE6cLmsEeBxM8fTAkwRAtFkAKCl0yDb+6kN7xoUAi9JW9mAtIAMPQCfQnvX
3ZOwOmeMPX7kchQL9mXJGtU=
=TSbX
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-25 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 23:41 Rafal Boni [this message]
2001-01-26 1:21 Bernd Eckenfels
2001-01-30 21:21 Rafal Boni
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=200101252341.SAA01008@ninigret.metatel.office \
--to=rafal.boni@edial.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®