-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

matthew sporleder <msporleder@gmail.com> writes:

> find / -name "*core*"  is how I would look for it.  :)

Yeah,  I didn't really want to do that, since it takes ~ forever,
but, I did it, and it didn't find a core, so it seems as though
one is not being left behind, and that's a little frustrating.

> Also, if you think it's crashing on a bad pixmap, I think you
> can run xlockmore in a window mode and test out individual
> screensavers it uses to see if one generates the crash,

Well, cycling through them manually and letting each one run for
a couple of seconds didn't unearth anything.  I suppose I'll have
to write a script and run a bunch for an extended period of time.

> On 5/16/05, segv <segv@netctl.net> wrote:
>> How about running it under ktruss:
>> 
>> ktruss -t A xclock 2>&1 | tee ~/xclock.ktruss

Well, with the exception of it being lock, not clock, I did this,
too, and it does appear that it's dying with a bad pixmap.  When
I came in this morning, xlock was not running any longer, and the
ktruss ended with:

X Error of failed request:  BadPixmap (invalid Pixmap parameter)
  Major opcode of failed request:  56 (X_ChangeGC)
  Resource id in failed request:  0x0
  Serial number of failed request:  709494193
  Current serial number in output stream:  709494197
  3951 ktruss   emul(netbsd)
  3951 ktruss	execve("/home/cwr/bin/rvplayer5.0/xlock", 0xbfbff2e4, 0xbfbff2ec) Err#2 ENOENT
  3951 ktruss	execve("/home/cwr/working/gated_tools/scripts/xlock", 0xbfbff2e4, 0xbfbff2ec) Err#2 ENOENT
  3951 ktruss   execve("/home/cwr/xlock", 0xbfbff2e4, 0xbfbff2ec) Err#2 ENOENT
  3951 ktruss   execve("/home/cwr/bin/xlock", 0xbfbff2e4, 0xbfbff2ec) Err#2 ENOENT
  3951 ktruss   execve("/home/cwr/scripts/xlock", 0xbfbff2e4, 0xbfbff2ec) Err#2 ENOENT
  3951 ktruss	execve("/home/cwr/working/achilles/working/xlock", 0xbfbff2e4, 0xbfbff2ec) Err#2 ENOENT
  
I'll try doing the window trick again for a longer period and see
if that gets me any farther.  In the meantime, any other
suggestions on debugging this problem are more than welcome.

Thanks,
Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFCi2eBP65RBOOHTzERAufGAKCWCaC9vFLZtdw7bsuWc/0h/lMy+wCbBKeU
BYSJNoyCi84q8TCP9GH5eaE=
=mgiw
-----END PGP SIGNATURE-----