[DGD] segmentation fault

[Par Winzell]

Nobody is suggesting you use rlimits as a hack to ignore the real 
problem. It's a lot easier to find your bug if DGD has a chance to print 
a stack trace rather than crashing. Only extremely well tested code 
should ever run without a stack limit.

On 2/12/08 12:10 PM, chris . wrote:
> I almost tried rlimits, but thought wouldn't rlimits simply be fixing a bug i created?  in other words
> if theres a bad loop somewhere shouldnt i try and resolve that?
> rlimits needs to be associated with a catch() right?  Ive never played with them, but i have a good
> realization of what they do.  I looked into them as a solution but opted to solve the 'real' problem.
> But maybe i misunderstand some aspect of dgd and rlimits.
> off the top of my head than, i would do something like
> catch() {rlimits(ST_SYSTEM_TICKS-1, ST_SYSTEM_MEMORY-1) { -subject code- } }
> 
> Is my bug because im not using rlimits where i should or because i have bad code?
> Well thanks:-)
> chris
> 
> _________________________________________________________________
> Connect and share in new ways with Windows Live.
> http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd