Subject: Re: Problem with gcore and permissions
To: None <darcy@NetBSD.org>
From: Andreas Wrede <email@example.com>
Date: 01/17/2005 19:29:14
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 17-Jan-05, at 5:22 PM, D'Arcy J.M. Cain wrote:
> On Tue, 11 Jan 2005 17:30:44 -0500
> "D'Arcy J.M. Cain" <darcy@NetBSD.org> wrote:
>>> | Note that gcore fails on -current as well. The gdb attach works
>>> | fine though. Unfortunately, so does PostgreSQL (it doesn't get
>>> | into a busy loop) so I can't use that to track down my PostgreSQL
>>> | problem.
>>> So the problem is fixed :-)
>> In -current, yes. But we can't leave our release in that state, can
>> That's why I am trying to debug this with the 2.0 branch instead of
>> release. I am hoping we can fix this for 2.0.1 or at least 2.1.
> It's possible that I have identified the change that fixes this. In
> src/sys/kern/sysv_sem.c the following was pulled up in ticket #903.
> Could this be the critical change? I am testing this now and so is
> Andreas Wrede (he was discussing this in the -help mailing list) so we
Unfortunately this change is not it. postgres went into a loop again
within 25 minutes of rebooting with the patched kernel. And again,
gcore produces 'gcore: ptrace(PT_DUMPCORE) failed: Permission denied'.
Note that gcore on a postgres process that is not looping works just
content-type: application/pgp-signature; x-mac-type=70674453;
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----