Re: [dev] operator delete mismatch

2010-04-10 Thread Terrence Enger
On Tue, 2010-03-30 at 13:51 +0200, Frank Schoenheit, Sun Microsystems Germany wrote: > Hi Terrence, > > > A website page about building OOo says that non-product builds are > > used almost exclusively within Sun. For a long time, I incorrectly > > took that to be a warning that they are hard to

Re: [dev] operator delete mismatch

2010-03-30 Thread Stephan Bergmann
On 03/30/10 13:31, Terrence Enger wrote: ( I think, though, that I am giving up on trying to use a non-product build when I actually want to get work done . ) :) That's exactly the reason why I want those non-pros to be effectively assertion free---which in turn I believe can only be achieve

Re: [dev] operator delete mismatch

2010-03-30 Thread Frank Schoenheit, Sun Microsystems Germany
Hi Terrence, > A website page about building OOo says that non-product builds are > used almost exclusively within Sun. For a long time, I incorrectly > took that to be a warning that they are hard to accomplish rather than > merely a description of a regrettable state of affairs. Perhaps we do

Re: [dev] operator delete mismatch

2010-03-30 Thread Terrence Enger
My thanks go to Stephan Bergmann, who also responded to my question. On Mon, 2010-03-29 at 15:00 +0200, Eike Rathke wrote: > Hi Terrence, > > On Friday, 2010-03-26 13:42:28 -0400, Terrence Enger wrote: > > > However, I have not found what library holds the object code for > > operators_new_dele

Re: [dev] operator delete mismatch

2010-03-29 Thread Eike Rathke
Hi Terrence, On Friday, 2010-03-26 13:42:28 -0400, Terrence Enger wrote: > However, I have not found what library holds the object code for > operators_new_delete.cxx. Let's see.. operators_new_delete.cxx is in sal/cpprt/, the sal/cpprt/makefile.mk says TARGET=salcpprt, then for "$(OS)" != "SOLA

Re: [dev] operator delete mismatch

2010-03-29 Thread Stephan Bergmann
On 03/26/10 18:42, Terrence Enger wrote: However, I have not found what library holds the object code for operators_new_delete.cxx. So it is hard to set a breakpoint to see what heap address is causing the assertion. (When a system library is calling delete or delete[], it is hard to work back

Re: [dev] operator delete mismatch

2010-03-26 Thread Terrence Enger
On Fri, 2010-03-19 at 15:15 +0100, Frank Schoenheit, Sun Microsystems Germany wrote: > Hi Terrence, > > > Since I created issue 110236 > > yesterday, I > > have encountered many occurrences. > > > > I have some time available. Do you have

Re: [dev] operator delete mismatch

2010-03-19 Thread Frank Schoenheit, Sun Microsystems Germany
Hi Terrence, > Since I created issue 110236 > yesterday, I > have encountered many occurrences. > > I have some time available. Do you have any suggestions about what this > means usually, it means somebody did something like char* foo

[dev] operator delete mismatch

2010-03-19 Thread Terrence Enger
Greetings, Since I created issue 110236 yesterday, I have encountered many occurrences. I have some time available. Do you have any suggestions about what this means or where I should start looking for an explanation or a solution? Cheer