> What bugs have you found with ELF? ELF works just fine for me, and most > other people using Linux, Sun and whatever else OS uses it. For most > people, ELF is not going to make much difference, unless you want to do > some run-time link and stuff like that. ELF doesn't have any more > hassles associated with it either as far as I know. I got Slackware > 3.0, got the new gdb, and everything is fine and dandy. aout is > beginning to fade away, and ELF is the new defacto(sp?) standard. > There's even been people suggesting removing aout support from the Linux > kernel altogether, this wont happen for quite a while yet, but it gives > you an idea of what aout is now. You'll see that pretty much anything > that is sold as executable only will mostly be ELF from now on (already is). Ok, the buglist: 1) ELF caught a bug that a.out let slip by, so that's a good thing, but was a bitch to hunt down. 2) My mud is crashing like a madman when one looting mob loots something. If I remove it's spec_proc, it runs fine... leave the spec in, it crashes. No I know how to code and I do it damn well, so you can believe me when I say I debugged the HELL out of that specproc. Wanna hear the best part? gdb tells me it crashed in: malloc (),... there IS NO malloc in that specproc. It's really dfrustrating... 3) For some reason, at a time which I cannot pinpoint, some chars on the mud are having their maxhit and maxmove numbers COMPLETELY destroyed... like 350 hps to 5, 120 maxmove to 12... and I cannot find a single thing to indicate why it would be happeneing. I have checked and rechecked and tripplechecked all code dealing with maxmove and maxhit... NONE of these bugs ever happened when I was on a.out... *suigh*
This archive was generated by hypermail 2b30 : 12/18/00 PST