I've now identified this as a problem with an editing context. I have
divided my system into multiple frameworks, since there are applications
which use only limited subsets of our overall system. Consequently
frameworks can load other frameworks and naturally there's one application
that uses most of the frameworks.
The core dump only occurs when I run this application (so far). There is a
point in the process where I want to insert a row into a database, without
saving any other changes. I do this by instantiating a new editing context,
creating the object and saving the changes. If I continue processing I
consistently get the core dump. I have found that if I invalidateAllObjects
before abandoning the editing context everything is fine.
Unfortunately invalidateAllObjects is slow, and I don't understand why I need
to use it.
Does anyone have an explanation for this behavior (I suspect it has something
to do with weak references)? How about an alternate solution?
Any insight is appreciated.
Todd
> -----Original Message-----
> From: Todd DeYoung
> Sent: Monday, October 07, 2002 1:39 PM
> To: [email protected]
> Subject: Mystery Abort
>
>
> I'm getting a core dump like error (see below) after going to sleep, but
> before coming awake. I don't even really know where else to look. Any
> ideas? Strategies?
>
> I'm using WO4.5sp3 running on Solaris.
>
> Thank you,
>
> Todd
>
> Todd A. DeYoung
> VP Research & Development
> UniTeller, Inc.
> 201.345.2070
>
ERROR:
SIGABRT 6* abort (generated by abort(3) routine)
si_signo [6]: SIGABRT 6* abort (generated by abort(3) routine)
si_errno [0]: Error 0
si_code [-1]: SI_LWP [pid: 5950, uid: 0]
stackbase=FDA0BCF8, stackpointer=FDA09EE4
<snip>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.