Going through and setting ulimit to unlimited really doesn't do a lot. In fact it won't do much of anything at all if you're using an RH system (at least with latest and greatest, I'm not sure about other versions): ---------------------------------------- ([EMAIL PROTECTED] 02:19:56): ~ ulimit unlimited ([EMAIL PROTECTED] 02:19:40): ~ ulimit unlimited ([EMAIL PROTECTED] 02:19:54): ~ ulimit -c 0 ([EMAIL PROTECTED] 02:19:56): ~ ----------------------------------------
To set the core size itself, use ulimit -c (coresize). For example ulimit -c unlimited would set your core size to an unlimited amount. BEWARE: This WILL reset once you log out of the system itself (I found this one out the hard way too). The best way to get this to stick in there is to put The above line in the bash_profile, .bashrc, or .whatevershellyouuserc. BEWARE TOO!! By setting your ulimit to unlimited, this can produce VERY nasty results!!! The latest versions of RH AND BSD (from what I've seen) use an odd way of dealing with core files. Instead of just one dump, they produce multiple dumps. This means that your core is no longer just core, it is core.number (haven't looked to see what the number represents).. This means you CAN have multiple core files, and they CAN be space consuming (believe me, I had a li'l problem with that one myself this morning). As far as progs go, I'll get off my tail and get a bit of a patch designed for stock rom sometime this week, hopefully, when I get around to it, sometime, yeah, maybe if I can find the time:P I know it's a major pain to deal with (took me quite the time to convert from olc2 to olc2+obj/room/mobprogs), but it IS possible. My suggestion: Start the mud up with gdb.. Read the FAQ for lessons in how to do that.. Once you do that, you can go through, step it out, and when it completely goes out, do a backtrace.. That'll point your problem to you! G'luck Nuff said! TJW :Head tech, designer, bum:P Mud :http://dreamless.gypsystar.com telnet :telnet://dreamless.gypsystar.com 9275 OLC Pages:http://olc.wolfstream.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Hill Sent: Thursday, June 27, 2002 1:13 AM To: [email protected] Subject: Re: No core file. Rats. It's not the Makefile. Are you sure that it's actually crashing and not just running into one of the many "exit(1)" conditions?? This is usually what I've seen when there is no core and the core limit is unlimited. Segmentation faults relating to roomprogs. Not "bug" in the logs :(. Any speech in the room with a 'speech' trigger, or, worse, being in a room with an ACT trigger causes the mud to seg fault. It's got me completely confuggled. If you'd like to help, I can post the do_say, p_act_trigger, and act_new goodies. I suspect the act code; it's given me shit before, so I'd be less than surprised if I fucked it up somewhere. Sigh. Sometimes the prog code is more of a handful than their worth; I like Death Gates' Script code muchly more, but alas, no ROM port of it. (the 'wait 20 s', etc stuff would be super useful!) -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
