Hi Stephan, Sure enough, rebooting the laptop solved the problem. I'm sure it wasn't an out-of-memory issue since everything else was running without complaint.
Cheers, Mark On 6/15/07, Stephan Bergmann <[EMAIL PROTECTED]> wrote:
Mark Greenbank wrote: > Hi, I'm trying to deploy an add-in (that was previously deployed without > error) and I'm getting the following error: > > /opt/openoffice.org2.2/program/unopkg add -f > /home/mark/src/OOPMTriStats/dist/OOPMTriStats.oxt > terminate called after throwing an instance of 'std::bad_alloc' > what(): St9bad_alloc > /home/mark/src/OOPMTriStats/nbproject/build-uno-impl.xml:135: exec > returned: > 134 > > Can anyone point me at some info in how to diagnose this? unopkg complains that there is not enough free memory in the process to satisfy some C++ new request. The typical cause is that there is a bogus new[n] somewhere in the code with badly large (e.g., uninitialized) n. Does the OOPMTriStats.oxt contain C++ code? If yes, it itself might be the culprit. Otherwise, you probably hit an error in unopkg. Is this reproducible? -Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
