🚀 go-pugleaf

In an earlier article, I wrote:
> Has anyone tried to use MallocDebug under NeXTSTEP 3.0?
> 
> I used it (once) under 2.x and it seemed to work OK.  I wanted to use
> it on a NS3.0 application, and if I link in the MallocDebug library
> then the program quits almost as soon as it starts.  No error messages
> or anything, it just quits.
> 
> Am I missing something?
> 
> The application that I'd like to MallocDebug is KPerfMon.app.  Maybe
> that particular app is doing something that MallocDebug isn't prepared
> to handle?

Thanks go to Tom McSorley for pointing me in the right direction.
He sent me a message which (basically) said:
| I experienced a similar problem to that indicated above.  All worked
| well under 2.x (not verifiable).  The application ran fine without
| the MallocDebug lib linked in under 3.0, however with the MallocDebug
| lib linked in, the application SEGMENTATION FAULTED immediately.
| Debugging this condition showed that the problem occurred before it
| ever got to any of my code -- therefore the problem was within the
| NIB file load and initialization.
| ... What it turned out to be was that the User Interface Guy used
| some fonts in his NIB file construction that were not present on the
| other system.  When we changed the fonts back to a system default font
| the SEGMENTATION FAULT disappeared.

In my case KPerfMon had two NIB files.  I removed an (unused) Services menu  
from the first, and fiddled around with the fonts in the second one (though  
I don't think I actually *changed* any fonts).  MallocDebug then worked like  
a charm.

I don't know if it was the fiddling I did, or if the NIB files just needed  
to be saved under a NS3.0 system...  In any case, I hope this info proves  
useful to anyone else who runs into a similar problem.  MallocDebug is  
pretty useful, now that I have the hang of it...

--
Garance Alistair Drosehn     =     gad@eclipse.its.rpi.edu
ITS Systems Programmer            (handles NeXT-type mail)
Rensselaer Polytechnic Institute;           Troy NY    USA

As people are getting the chance to play with the 3.0 MallocDebug,
perhaps someone has come up with an answer to a question I asked a
while ago but got no answer to. Is there any way to use MallocDebug on
an application that runs under something else, and so doesn't show up
as an application in its own right in the workspace? I'm trying to
find a malloc problem in multi-window Lucid emacs 19.3, running under
co-Xist, and I need all the help I can get. I compiled and linked it
the way you're supposed to to use MallocDebug, but since it doesn't
show up in the right way, I don't any return on that effort.

--Steve Anderson