-xprofile=use postopt has assertion failure

i got the following assertion failure while trying to link a shared library with -xprofile=use (and -xipo=2 -xlinkopt=2):
$ /usr/local/stow/sunstudio10/bin/CC  -fast -xipo=2 -xjobs=5 -xprefetch -xlinkopt=2 -xprofile=use:runsim -KPIC -features=extensions -xtarget=ultra3cu -xarch=v9a -G -xtarget=ultra3cu -xarch=v9a -o libsparcsulima.so [lots of .o files] -lCstd -lCrun -lsocket -lelf
CC: Fatal error in postopt: Abort (core dumped)
postopt: assertion failed: at line 351 in file "../src/generic/infrastructure/exception_handler.cc"
postopt: Invalid symbol referenced in exception relocation entryi have saved the core file, if that might be useful.

To address this problem, we would need a test case that demonstrates the failure. The core dump would not show what caused the assertion.
If you have a service contract with Sun, please file a bug report via your support channel. They will request a test case, and we can keep the code confidential if necessary.
If you don't have a service contract, let me know if the email address in your profile is valid, and if so, I'll contact you.
But the best way to address bugs in the product is through Sun Service. Although people don't always believe me when I say it, back channels are actually less effective than going in the front door.

Similar Messages

  • Assertion failure error while using hierarchy column in 11.1.1.7.1

    Hi all,
    I have done In-place upgrade of OBIEE from 11.1.1.5 to 11.1.1.7. Afterthat installed 11.1.1.7.1 patchset also.
    Dashboard prompts were created by using hierarchy column. While applying hierarchy prompt i am getting below error
    Assertion failure: levels.size() > start_pos at line 843 of project/weblayoutbuilder/viewlayoutbuilderutil.cpp
      Error Details
    Error Codes: ACIOA5LN
    Some times presentation services will restarted automatically.
    Kindly give a solution regarding this.
    Thanks in advance

    This is occuring due to Bug 17334677 in 11.1.1.7.0. It has been fixed in future versions and backported to SOA BPM 11.1.1.7.0 Apply Patch 17334677

  • Been using Lightroom 5.6 for weeks, no issues.  Went to open a catalogue today, it would not open... message assertion failure. Followed Adobe's posted fix... still cannot open catalogue or Lightroom at all. Running Windows 7. Help!

    I have been using Lightroom 5.6 for weeks. Today I went to open a catalog and I got the message "assertion failure". I have gone through Adobe's posted fix for this, the Pictures folder is linked to My Pictures folder. Still no luck, in fact Light room will not open at all. I get the name of the catalog, I tried to open earlier, across my screen and the message "assertion failure". I am running Windows 7. Does anyone know of a fix for this??

    Reset your preferences file: Resetting (or 'Trashing') the Lightroom Preferences file - Lightroom Forums

  • Assertion Failures using Mail.app with Exchange 2007...

    We have been implementing and migrating our end-users to Exchange 2007. In doing so we found that Mail.app end-users were experiencing Assertion failures in Console.app. They used to cause Mail.app to crash and lose connectivity frequently to the Exchange 2007 server. We made a change to the firewall to allow communication to happen between domain controllers, but haven't been able to determine if this in fact resolved or helped hide the root cause. We seem to be no longer crashing Mail.app or losing connectivity, but the same logs when we would crash/lose connectivity are still happening when you look in Console.app.
    *Here is an example of an Assertion failure where "The Operation couldn't be completed":*
    +11/12/10 1:19:36 PM Mail[3201] * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSConnection.m:374+
    +Received an unexpected error: Error Domain=NSXMLParserErrorDomain Code=5 "The operation couldn’t be completed. (NSXMLParserErrorDomain error 5.)", response: (null)+
    + 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
    + 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
    + 2 Message 0x00007fff8036301b -[EWSConnection sendMessage:forRequest:] + 1117+
    + 3 Message 0x00007fff8036e5b9 -[EWSGateway sendMessage:forRequest:] + 79+
    + 4 Message 0x00007fff80381a63 -[EWSRequestOperation executeOperation] + 104+
    + 5 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
    + 6 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
    + 7 Foundation 0x00007fff8662abeb __doStart2 + 97+
    + 8 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
    + 9 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
    + 10 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
    + 11 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
    *I also get this Assertion failure every time I re-open Mail.app that shows up in Console.app that says "Mail did something wrong: The specified folder could not be found in the store.":*
    +11/12/10 12:44:22 PM Mail[3201] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
    +Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x1012f1830> (EXECUTING)+
    + 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
    + 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
    + 2 Message 0x00007fff80382956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295+
    + 3 Message 0x00007fff80377aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88+
    + 4 CoreFoundation 0x00007fff879c26d7 __NSArrayEnumerate + 1399+
    + 5 Message 0x00007fff80377d86 -[EWSGetFolderResponseOperation executeOperation] + 445+
    + 6 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
    + 7 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
    + 8 Foundation 0x00007fff8662abeb __doStart2 + 97+
    + 9 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
    + 10 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
    + 11 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
    + 12 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
    +11/12/10 12:44:22 PM Mail[3201] Recieved EWS error: Error Domain=MFEWSErrorDomain Code=79 UserInfo=0x1148c1d10 "The specified folder could not be found in the store."+
    We are getting these Assertion Failures for other end-users as well that are using Mail.app and connecting to Exchange 2007 Server. I have wiped my mail.app account and started from fresh and that didn't help. I did it manually as well ensuring that preference files, caches, and passwords related to mail.app, ical.app, and Address Book.app were removed. That did not work. I just went from 10.6.4 to 10.6.5 hoping that would correct the issue, it did not. I even set up on another Mac a baseline Snow Leopard and patched it and then configured my mail account and still got the same errors.
    What I am hoping for is not a miracle (Fixing the problem), but being told what these errors mean and if there is any risks to be concerned with. In other words, can I ignore these error messages or should I be concerned? Like I said it was causing us to get the sideways thunderbolt or triangle with an exclamation point and even crashing Mail.app at times. That hasn't happened since we let the all of the domain controllers talk to each other, even though they shouldn't have to.

    I echo your hope for someone shedding a light on this. I too am geting Assertion failures, every few days, though without much in the way of crashes.
    Here is an example of a log entry describing one recent such failure:
    +5.12.2010 11:04:40 Mail[17075] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
    +Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x11d80ec70> (EXECUTING)+
    0 Message 0x00007fff81f7d6e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
    1 Message 0x00007fff81f7d649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
    2 Message 0x00007fff81ede956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295
    3 Message 0x00007fff81ed3aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88
    4 CoreFoundation 0x00007fff8448c6d7 __NSArrayEnumerate + 1399
    5 Message 0x00007fff81ed3d86 -[EWSGetFolderResponseOperation executeOperation] + 445
    6 Message 0x00007fff81f8bab9 -[MonitoredOperation main] + 229
    7 Foundation 0x00007fff847b4de4 -[__NSOperationInternal start] + 681
    8 Foundation 0x00007fff84893beb __doStart2 + 97
    9 libSystem.B.dylib 0x00007fff85f6b2c4 dispatch_call_block_andrelease + 15
    10 libSystem.B.dylib 0x00007fff85f49831 dispatch_workerthread2 + 239
    11 libSystem.B.dylib 0x00007fff85f49168 pthreadwqthread + 353
    12 libSystem.B.dylib 0x00007fff85f49005 start_wqthread + 13
    Perhaps coincidentally, I am having trouble with syncing iCal with my Exchange account. Ii have only found this thread on the subject, and am in the process of trying to find there the solution to that problem:
    http://discussions.apple.com/thread.jspa?threadID=2138051
    Any and all insight would be greatly appreciated.

  • Apple Mail Assertion Failure

    Hi,
    My company uses Office 365 for hosted Exchange email. We have 1 user who uses Apple Mail on OSX 10.7 to connect to the server in Exchange mode (using EWS). This was working great until a few days ago where he has sporadic connection problems. Reproducable situation below:
    1) Select 100 emails in any given folder
    2) Drag/drop those emails into another folder to move them there
    3) They will start moving but it will fail at somepoint and give the message "Cannot execute move operation".
    4) After that message appears it is usually several minutes before he can try again or send any emails.
    5) Trying to send an email immediately after the error message results in the "Cannot send message using the server" dialog where you are prompted to select a different server to send the message. Choosing an SMTP server results in the message being sent but sometimes (and only sometimes) the message is resent a couple of hours later through the exchange system.
    We are getting a million of the following assertion failure messages in the console:
    06-06-2012 12:22:05.518  Mail: *** Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSResponseOperation.m: 340
    EWS did something wrong: An internal server error occurred. The operation failed. on EWS response <EWSGetFolderResponseOperation: 0x7fb9cb1ae620> (EXECUTING)
    0   Message 0x00007fff8f712ef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
    1   Message 0x00007fff8f71308e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
    2   Message 0x00007fff8f662c64 -[EWSResponseOperation handleResponseMessage:withObject:] + 556
    3   Message 0x00007fff8f656eb6 __-[EWSGetFolderResponseOperation executeOperation]_block_invoke_1 + 77
    4   CoreFoundation 0x00007fff87979cee __NSArrayEnumerate + 718
    5   Message 0x00007fff8f6572ae -[EWSGetFolderResponseOperation executeOperation] + 453
    6   Message 0x00007fff8f73397f -[MonitoredOperation main] + 228
    7   Foundation 0x00007fff9152e6b4 -[__NSOperationInternal start] + 705
    8   Foundation 0x00007fff91541912 ____NSOQSchedule_block_invoke_2 + 124
    9   libdispatch.dylib 0x00007fff8a798a86 _dispatch_call_block_and_release + 18
    10  libdispatch.dylib 0x00007fff8a799965 _dispatch_worker_thread2 + 255
    11  libsystem_c.dylib 0x00007fff8c83b3da _pthread_wqthread + 316
    12  libsystem_c.dylib 0x00007fff8c83cb85 start_wqthread + 13
    06-06-2012 12:22:05.518  Mail: Recieved EWS error: Error Domain=MFEWSErrorDomain Code=94 "An internal server error occurred. The operation failed." UserInfo=0x7fb9cecbb7c0 {NSLocalizedDescription=An internal server error occurred. The operation failed.}
    We have tried deleting the account and making a new one. As well as removing the mailbox folder (~/Library/Mail/V2/EWS-*) and the Apple Mail plist file. We have also setup the email on a different Mac (also OSX 10.7) but we still get the same assertion failure message.
    This user's email account works fine in Outlook on Windows and Mac (Outlook 2010 and 2011) and it also works fine through the online web portal. Outlook 2011 Mac uses EWS (the same protocol Apple Mail uses) and it's not throwing any errors and everything works properly so that is leading me to believe it's an issue with Apple Mail.
    Perhaps related, perhaps not, but the user's iPhone and iPad have also stopped working properly with the account. They will sometimes connect but a lot of the time they give an error message about not being able to connect to the server. This leads us to believe it's an exchange server problem, but then why does it work in Outlook and the online portal without any problems? It's only the Apple products that are falling apart.

    I ended up having to reproduce the problem in Outlook 2011 Mac before O365 support would help me. Apparently Apple Mail isn't one of the officially supported clients so they weren't going to figure it out for me. Once they ran out of ideas they just gave me the "Apple Mail is officially supported" excuse and stopped helping me.
    Although we weren't initially having the problem in Outlook 2011 Mac it did start giving tons of errors during certain operations (with a -19907 error code) after a while. Not sure why it started doing that ... but it did. This was only happening with one of our user's accounts so it had to be something server-side that was the problem. I eventually got a support ticket in their system (despite being a P1 plan holder) so that they could call me. We did some Wireshark capturing to try to diagnose the problem but by that time the problem had fixed itself.

  • SDO_MVCLIENT throws occasional Aurora assertion failure error ORA-29516

    Hi folks,
    Occasionally I seem to receive the follow error when using the SDO_MVCLIENT package to run Mapviewer. The problem goes away if I just resubmit the job.
    Warning: ociexecute() [function.ociexecute]: ORA-29516: Aurora assertion failure: Assertion failure at joeintp.c:373 Interpreter hit null Java opcode. ORA-06512: at "MDSYS.SDO_MVCLIENT", line 393 ORA-06512: at "PDZIEMIELA.TW_PHP", line 553 ORA-06512: at line 1 in C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\tw.php on line 294
    Line 393 in the package is
    FUNCTION run RETURN VARCHAR2 AS LANGUAGE JAVA NAME 'oracle.lbs.mapclient.SQLMapClient.run() return java.lang.String';
    So I am thinking this has to do with java. Could I have muff the loadjava somehow? I followed all the steps. Any thoughts? This is on a 64 bit Solaris 10 machine. The system has JDK 1.5 in the path but oracle has JDK 1.4 in its directory tree under jdk.
    Thanks!
    Paul

    Also just a note as you don't specify which database version you are running but in 8.1.7 the return buffer does not seem to be managed correctly by the database as once removing a message from the buffer it still remains on the buffer.
    The only work around I've found, so far, is to manipulate Utl_Tcp.Connection.private_bf using utl_raw.
    Under 9i this is not an option as private_bf is non-existant in Utl_Tcp.Connection

  • FlexUnit 4 assert failures have "explosive" stack traces

    With FlexUnit 4 in Flash Builder 4 Plugin Beta, I created 1 suite with 1 class with 1 default failing test method. When I ran it, the assert failure had a call stack 60 methods high. Is this a bug?
    The stack trace has several "async" methods, e.g. applyExplosivelyAsync(). This seems strange because  I'm not using async at all. Is this intended behavior?
    Robert
    Test method Not yet implemented
           at flexunit.framework::Assert$/
    fail()[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\fluint\FlexU nit1Lib\src\flexunit\framework\Assert.as:370]
            at WidgetTest/testWidget()[C:\Users\robert.penner\Adobe Flash Builder
    Plug-in Beta 2\TestProject\src\WidgetTest.as:20]
            at Function/http://adobe.com/AS3/2006/builtin::apply()
            at flex.lang.reflect::Method/apply()[C:\Users\mlabriola\Documents\workspaces\net\digitalprim ates\opensource\flexunit\FlexUnit4\src\flex\lang\reflect\Method.as:124]
            at ReflectiveCallable/run()[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\open source\flexunit\FlexUnit4\src\org\flexunit\runners\model\FrameworkMethod.as:214]
            at org.flexunit.runners.model::FrameworkMethod/applyExplosivelyAsync()[C:\Users\mlabriola\Do cuments\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\runn ers\model\FrameworkMethod.as:121]
            at org.flexunit.runners.model::FrameworkMethod/invokeExplosivelyAsync()[C:\Users\mlabriola\D ocuments\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\run ners\model\FrameworkMethod.as:132]
            at org.flexunit.internals.runners.statements::InvokeMethod/evaluate()[C:\Users\mlabriola\Doc uments\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\inter nals\runners\statements\InvokeMethod.as:52]
            at org.flexunit.internals.runners.statements::StackAndFrameManagement/evaluate()[C:\Users\ml abriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\fle xunit\internals\runners\statements\StackAndFrameManagement.as:94]
            at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[C:\Users\mlab riola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexu nit\internals\runners\statements\StatementSequencer.as:62]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.token::AsyncTestToken/sendResult()[C:\Users\mlabriola\Documents\workspaces\n et\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\token\AsyncTestToken.as: 70]
            at org.flexunit.internals.runners.statements::AsyncStatementBase/sendComplete()[C:\Users\mla briola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flex unit\internals\runners\statements\AsyncStatementBase.as:44]
            at org.flexunit.internals.runners.statements::StatementSequencer/sendComplete()[C:\Users\mla briola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flex unit\internals\runners\statements\StatementSequencer.as:103]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:86]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[C:\Users\mlab riola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexu nit\internals\runners\statements\StatementSequencer.as:62]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.runners::BlockFlexUnit4ClassRunner/runChild()[C:\Users\mlabriola\Documents\w orkspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\runners\Block FlexUnit4ClassRunner.as:104]
            at org.flexunit.internals.runners::ChildRunnerSequencer/executeStep()[C:\Users\mlabriola\Doc uments\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\inter nals\runners\ChildRunnerSequencer.as:49]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[C:\Users\mlab riola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexu nit\internals\runners\statements\StatementSequencer.as:62]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.token::AsyncTestToken/sendResult()[C:\Users\mlabriola\Documents\workspaces\n et\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\token\AsyncTestToken.as: 70]
            at org.flexunit.internals.runners.statements::AsyncStatementBase/sendComplete()[C:\Users\mla briola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flex unit\internals\runners\statements\AsyncStatementBase.as:44]
            at org.flexunit.internals.runners.statements::StatementSequencer/sendComplete()[C:\Users\mla briola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flex unit\internals\runners\statements\StatementSequencer.as:103]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:86]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[C:\Users\mlab riola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexu nit\internals\runners\statements\StatementSequencer.as:62]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.runners::ParentRunner/run()[C:\Users\mlabriola\Documents\workspaces\net\digi talprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\runners\ParentRunner.as:315]
            at org.flexunit.runners::Suite/runChild()[C:\Users\mlabriola\Documents\workspaces\net\digita lprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\runners\Suite.as:59]
            at org.flexunit.internals.runners::ChildRunnerSequencer/executeStep()[C:\Users\mlabriola\Doc uments\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\inter nals\runners\ChildRunnerSequencer.as:49]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[C:\Users\mlab riola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexu nit\internals\runners\statements\StatementSequencer.as:62]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.token::AsyncTestToken/sendResult()[C:\Users\mlabriola\Documents\workspaces\n et\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\token\AsyncTestToken.as: 70]
            at org.flexunit.internals.runners.statements::AsyncStatementBase/sendComplete()[C:\Users\mla briola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flex unit\internals\runners\statements\AsyncStatementBase.as:44]
            at org.flexunit.internals.runners.statements::StatementSequencer/sendComplete()[C:\Users\mla briola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flex unit\internals\runners\statements\StatementSequencer.as:103]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:86]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[C:\Users\mlab riola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexu nit\internals\runners\statements\StatementSequencer.as:62]
            at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete( )[C:\Users\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit 4\src\org\flexunit\internals\runners\statements\StatementSequencer.as:82]
            at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[C:\Users\mlabrio la\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit \internals\runners\statements\StatementSequencer.as:68]
            at org.flexunit.runners::ParentRunner/run()[C:\Users\mlabriola\Documents\workspaces\net\digi talprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\runners\ParentRunner.as:315]
            at org.flexunit.runner::FlexUnitCore/beginRunnerExecution()[C:\Users\mlabriola\Documents\wor kspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\runner\FlexUnit Core.as:177]
            at org.flexunit.token::AsyncListenersToken/sendReady()[C:\Users\mlabriola\Documents\workspac es\net\digitalprimates\opensource\flexunit\FlexUnit4\src\org\flexunit\token\AsyncListeners Token.as:59]
            at org.flexunit.runner.notification.async::AsyncListenerWatcher/sendReadyNotification()[C:\U sers\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\ org\flexunit\runner\notification\async\AsyncListenerWatcher.as:87]
            at org.flexunit.runner.notification.async::AsyncListenerWatcher/handleListenerReady()[C:\Use rs\mlabriola\Documents\workspaces\net\digitalprimates\opensource\flexunit\FlexUnit4\src\or g\flexunit\runner\notification\async\AsyncListenerWatcher.as:97]
            at flash.events::EventDispatcher/dispatchEventFunction()
            at flash.events::EventDispatcher/dispatchEvent()
            at flexunit.flexui::FlexUnit4TestRunner/handleConnect()[C:\work\flex\ide_builder\com.adobe.f lexbuilder.flexunit\flexunitframework\src\flexunit\flexui\FlexUnit4TestRunner.as:296]
            at flash.events::EventDispatcher/dispatchEventFunction()
            at flash.events::EventDispatcher/dispatchEvent()
            at flash.net::XMLSocket/reflectEvent()

    Not a bug and fully expected behavior.
    FlexUnit 4 is really just a collection of runners that can handle just about anything that is thrown at it as well as handle any pluggable runners that others write. The level of extensibility comes with some complexity. So, by the time that single method of yours is executed, there are actually probably a hundreds methods in the framework for getting everything setup, inspected and ready to go.
    The stacktrace always looks up the stack from your failure to the last point where a particular chunk of code execution began, so the 60 is basically just that number of methods. There isn't a whole lot that can be done about it save for eventually provinding filtering to eliminate showing some of our stuff and making the track more legible.
    Regarding the async thing, your method isn't async but FlexUnit4 is. Inside of the Flash Player we are operating on frames. We don't have the luxury of threads and the like that Java has, so we have to handle the possibility that something might be async on a much deeper level. We also do something called green threading where we actually watch how much time we take in execution. Once we have taken 90% ish of the time available in a given frame, we wait until the next one before we begin executing again. This allows us to run long and compelx test suites without getting a timeout from the flash player (which happens if any single frame takes longer than 15 seconds to execute). So, even though your method isn't doing anything async, all of these other pieces have to account for the chance that something will be. Hence the reason that you see async pieces in the stack trace.
    Hope that helps,
    Mike

  • Loadjava gives ORA-29516: Assertion failure at eox.c:232

    I was trying to test on the loadjava and Java Stored Procedure capabilities on Oracle 9i Release 2.
    I ran into the following error when I tried to load a number of Oracle jar library files into the database (in order to resolve my class using org.apache.soap packages).
    Error while computing shortname of org/apache/soap/Utils
    ORA-29516: Aurora assertion failure: Assertion failure at eox.c:232
    Uncaught exception Root of all Java exceptions: java.lang.NullPointerException
    ORA-06512: at "SYS.DBMS_JAVA", line 213
    ORA-06512: at line 1
    I ran the following command:
    loadjava -thin -user system/manager@<host>:1521:local -resolve -synonym -verbose -grant public
    D:/jdev9i/soap/lib/soap.jar D:/jdev9i/lib/dms.jar D:/jdev9i/jlib/javax-ssl-1_1.jar
    C:/ora81/lib/servlet.jar D:/jdev9i/jdk/jre/lib/ext/mail.jar
    Does anyone has any idea how I can resolve this problem? Response is appreciated. Thanks!

    I have Oracle-DB Server on Linux and Windows-2000.
    I try to deploy the Java-Function to Oracle-DB with JDevelopr.
    My Email: [email protected]
    Here are my deploy-Preview:
    -user
    <connect string>
    -order
    -resolve
    -noverify
    -debug
    -definer
    -force
    -synonym
    -verbose
    thanks
    MZ

  • Solaris Studio 12.4 Beta ube assertion failure with -m64 -fsimple

    I have found a way to get an assertion failure from the ube program that comes with the Solaris Studio 12.4 beta.  The error that gets printed is:
    assertion failed in function gra_peep_hole() @ gra.c:10381
    assert(lf_op_(lf_i) == LD_I)
    The problem occurs whilst compiling a 64 bit version of GNU tar 1.23 using the -fsimple option on the C compiler.
    This problem can be reproduced by getting the pre-processed code I've put on http://pastebin.com/wRHRmaiT and pasting it into a file called human.pre.c.  Then run:
    cc -std=c99 -m64 -mt -O4 -fsimple -c -o human.o human.pre.c
    and you get the assertion failure.
    Alternatively, if you don't trust my code on pastebin, the other way to reproduce it would be to download tar-1.23.tar.gz from GNU Project Archives, extract it and then you'll find the original file human.c in the gnu sub-directory.  Build this with:
    cc -std=c99 -DHAVE_CONFIG_H -I. -I.. -m64 -mt -O4 -fsimple -c -o human.o human.c
    and you'll get the same problem.
    The assertion failure only happens with -m64 and -fsimple.  If either of these flags are omitted it doesn't happen.
    People reading this will probably think I'm crazy to be worrying about floating point optimisations for GNU tar, and it's true that I don't really need to build GNU tar with -fsimple.  However, I am worried that the same problem in ube will bite me at some point on more important code where floating point optimisations are valuable.
    In case it's relevant, I'm working on Oracle Solaris 10 1/13 s10x_u11wos_24a X86.

    BugID 18644770 has been fixed recently and the fix is verified with this problem:
    [sr1-sfbay-03](18644770)-627 > /net/dv103/export/builds/cia//latest/inst/intel-S2/bin/cc -std=c99 -m64 -mt -O4 -fsimple -c human.pre.c -V
    cc: Sun C 5.13 SunOS_i386 CIA_pythia 2014/06/16
    acomp: Sun C 5.13 SunOS_i386 CIA_pythia 2014/06/16
    iropt: Sun Compiler Common 12.4 SunOS_i386 CIA_pythia 2014/06/16
    ube: Sun Compiler Common 12.4 SunOS_i386 CIA_pythia 2014/06/16
    as: Sun Compiler Common 12.4 SunOS_i386 CIA_pythia 2014/06/16
    [sr1-sfbay-03](18644770)-628 >
    This fix should be available soon as the Studio12.4 Beta refresh compiler.

  • Assertion failure from ccfe in Solaris Studio 12.4 beta July refresh

    I have found a way to get an assertion failure from the ccfe program that comes with the Solaris Studio 12.4 beta July refresh.  The error that gets printed is:
    >> Assertion:   (../lnk/funcsym.cc, line 1679)
        while processing text_woarchive.pre.cpp at line 0.
    The problem occurs whilst compiling Boost 1.54.  The original file in the distribution that causes it is libs/serialization/src/text_woarchive.cpp.
    This problem can be reproduced by getting the pre-processed code I've put on http://pastebin.com/E9vxi2z7 and pasting it into a file called text_woarchive.pre.cpp.  Then run:
    CC -std=c++11 -mt -m64 -c -o text_woarchive.o text_woarchive.pre.cpp
    and you get the assertion failure.
    Running:
    CC '-#' -std=c++11 -mt -m64 -c -o text_woarchive.o text_woarchive.pre.cpp
    shows that the assertion is coming from ccfe.
    In case you go back to the original Boost source code I should tell you that prior to generating the pre-processed source I changed:
    #ifdef __SUNPRO_CC
    to:
    #if 0
    in boost/archive/detail/register_archive.hpp.  I did this because there was an error in the __SUNPRO_CC section and I wondered if that workaround code was no longer required with the more modern C++ compiler.  Therefore, I cannot guarantee that the pre-processed source is 100% valid C++ code.  However, even if it's not it would be nice to get a clear error message out of ccfe rather than an assertion failure.
    In case it's relevant, I'm working on Oracle Solaris 10 1/13 s10x_u11wos_24a X86.

    You mentioned in the other answer that you are testing with Boost 1.55.  Are you testing this in C++11 mode?
    Today I downloaded Boost 1.55 and did the following:
    In both tools/build/v2/engine/build.sh and tools/build/v2/tools/sun.jam globally replace SUNWspro with SolarisStudio12.4-beta_jul14-solaris-x86
    In tools/build/v2/tools/sun.jam replace:
    feature.extend stdlib : sun-stlport ;
    feature.compose <stdlib>sun-stlport
        : <cxxflags>-library=stlport4 <linkflags>-library=stlport4
    with:
    feature.extend stdlib : sun-stlport ;
    feature.compose <stdlib>sun-stlport
        : <cxxflags>-std=c++11 <linkflags>-std=c++11
    Note: This is just the quick way I found to con the Boost build system into using C++11 instead of STLport.  The feature in the jam file still has stlport in its name, but that's only a name and the code is being built in C++11 mode.
    In boost/math/special_functions/detail/lanczos_sse2.hpp change line 15 from:
    #if defined(__GNUC__) || defined(__PGI)
    to:
    #if defined(__GNUC__) || defined(__PGI) || defined(__SUNPRO_CC)
    Run:
    ./bootstrap.sh --without-libraries=context --without-libraries=coroutine --without-libraries=graph_parallel --without-libraries=log --without-libraries=mpi --without-libraries=python --without-libraries=test --without-icu
    Run:
    ./b2 -j4 --layout=versioned --disable-icu address-model=64 threading=multi optimization=speed inlining=full
    At this point the vast majority of the code builds, but does not link.
    There are 3 problems:
    The compilation problem with tuple that you've already fixed
    A linker problem with finding std::string related symbols - maybe also related to the gcc header upgrade and now fixed?
    Numerous compilation problems caused by boost/archive/detail/register_archive.hpp
    For this last one the code in the #ifdef __SUNPRO_CC section of boost/archive/detail/register_archive.hpp does appear to be invalid, and leads to the errors:
    "./boost/archive/detail/register_archive.hpp", line 45: Error: The function "adjust_counter" must have a prototype.
    "./boost/archive/detail/register_archive.hpp", line 46: Error: Expression must have a constant value.
    "./boost/archive/detail/register_archive.hpp", line 47: Error: Expression must have a constant value.
    "./boost/archive/detail/register_archive.hpp", line 48: Error: An integer constant expression is required within the array subscript operator.
    Even with Boost 1.55, attempts to fix this lead to the same ccfe assertion.  Trying to use the #else part of the code as I described in the original post does, as does moving the line:
    char adjust_counter(counter<0>);
    so that it comes before the place where adjust_counter is used also then leads to the same assertion:
    >> Assertion:   (../lnk/funcsym.cc, line 1679)
    It's as though any change to boost/archive/detail/register_archive.hpp that fixes the basic code ordering issue lets ccfe get far enough to cause the assertion.
    If there is somebody in your team looking at whether Boost 1.55 compiles with Solaris Studio 12.4 in C++11 mode then hopefully they can relate to what I'm seeing here.  One key point is that they'll have had to edit the jam files to use C++11 mode.
    The other thing is that any insights the person who has been trying to build Boost 1.55 has would be very useful.  I know you don't want to get into officially supporting it, but maybe a blog post with any unofficial hints and tips on getting Boost to build in C++11 mode could be a way to share knowledge.

  • Aurora Assertion Failure Error

    I tried to run a pl/sql program using utl_tcp.
    It's giving error like this:
    DECLARE
    ERROR at line 1:
    ORA-29516: Aurora assertion failure: Assertion failure at eox.c:187
    Uncaught exception Root of all Java exceptions:
    ORA-06512: at "SYS.UTL_TCP", line 533
    ORA-06512: at "SYS.UTL_TCP", line 514
    ORA-06512: at line 22
    ORA-29516: Aurora assertion failure: Assertion failure at eox.c:187
    Uncaught exception Root of all Java exceptions::
    JVM has been installed properly as seen from the count of objects which is around 8648.
    Pls help me.

    Also just a note as you don't specify which database version you are running but in 8.1.7 the return buffer does not seem to be managed correctly by the database as once removing a message from the buffer it still remains on the buffer.
    The only work around I've found, so far, is to manipulate Utl_Tcp.Connection.private_bf using utl_raw.
    Under 9i this is not an option as private_bf is non-existant in Utl_Tcp.Connection

  • How to backtrace an assertion failure?

    If an assert() fails during the execution of the program, there doesn't seem to be any way of backtracing the function call stack up to that point. If I open the console from the 'Run' menu and try to write 'bt', it doesn't let me. gdb seems to be in a strange state where you can write just one character and then it's stuck until you press return, after which nothing happens. Backtracing works ok if eg. the program crashes with a segmentation fault, but it doesn't work if it crashes with an assertion failure.
    This is extremely irritating. I have a bug in my program which is causing an assertion failure very, very rarely (making it extremely hard to reproduce), and in the very rare occasions where it's happening, I can't find the exact chain of function calls leading to that failure because xcode won't let me backtrace. (And no, the file/line where the assertion failure is happening, which xcode is reporting, is not helpful in this particular case because it's being called from many different places.)

    Is it even possible to do any other type of programming for the iPhone than Cocoa Touch?
    Anyways, I cannot control all instances of assert() being called because some of them may be coming from the gcc C++ standard library implementation (mainly when GLIBCXXDEBUG has been defined). Rather obviously, when that happens, a backtrace would be really useful to see exactly which line caused the assert() inside the library to fail, especially if it happens inside a library function not directly called from my code (but by other library code) and/or when it's called from very many different locations in my code.
    But it's not just a problem with an assert() failing inside the C++ libraries. Any assert() in my own code causes the exact same behavior, and sometimes it's rather irritating not being able to get a backtrace, especially if it happens extremely rarely and thus is very hard to replicate. This even when building in debug mode.

  • Mail and Exchange 2007 Assertion Failure

    I have been using Mail with Exchange 2007 on SL since it came out without issue, until last week. Once I start Mail I experience the following issues:
    1. Mail folders sometimes show as empty. Occasionally synchronizing the account corrects the issue, but often I need to restart Mail.
    2. Messages are duplicated in my Inbox. The only way to correct this is to delete and readd my account.
    3. Sent mail creates a draft message after the message has been sent. This usually goes away in 5-10 minutes of normal use.
    4. I get the following error message around 5 times per second in the system log while Mail is open and connected to Exchange:
    Mail[718]: * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1077/MessageStores.subproj/EWSConnection.m:374\nRe ceived an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 UserInfo=0x118be9740 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)", response: (null)\n(\n 0 Message 0x00007fff86b70119 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137\n 1 Message 0x00007fff86b7007e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220\n 2 Message 0x00007fff86ab2fbe -[EWSConnection sendMessage:forRequest:] + 1117\n 3 Message 0x00007fff86abe0ec -[EWSGateway sendMessage:forRequest:] + 79\n 4 Message 0x00007fff86ad0fbf -[EWSRequestOperation executeOperation] + 104\n 5 Message 0x00007fff86b7e347 -[MonitoredOperation main] + 229\n 6 Foundation 0x00007fff8270f06d -[__NSOperationInternal start] + 681\n 7 Foundation 0x00007fff8270ed23 ___startOperations_block_invoke2 + 99\n 8 libSystem.B.dylib 0x00007fff84e0fce8 dispatch_call_block_andrelease + 15\n 9 libSystem.B.dylib 0x00007fff84dee279 dispatch_workerthread2 + 231\n 10 libSystem.B.dylib 0x00007fff84dedbb8 pthreadwqthread + 353\n 11 libSystem.B.dylib 0x00007fff84deda55 start_wqthread + 13\n)
    I have only seen one person report this issue so far and the fix was to remove /Library/Preferences/com.apple.mail.plist. I tried that, but the issue was not resolved.
    I am running Mail 4.2 on Snow Leopard 10.6.2 on a MBP 15" unibody. Any help is appreciated.

    I too have been using Mail.app x Exchange 2007 since SL came out without issue. Very similar issues started exhibiting themselves last week for me, as well:
    1. Mail folders sometimes show as empty (including the inbox). A restart of Mail fixes this.
    2. New messages occasionally only show headers. A restart of Mail fixes this.
    3. Mail will occasionally hang forever retrieving new messages.
    4. Sending a message will occasionally return a failure message, when it was, in fact, delivered. If I choose to "Send Later", a duplicate message is immediately sent.
    #1-3 are annoyances, #4's caused me to switch away from Mail.app--comes across as incredibly unprofessional to my user base and associates.
    Here's just one of the hundreds of messages that appears in Console (these literally pop up every 2-5 seconds I have Mail.app open..):
    3/11/10 3:25:05 PM Mail[30150] * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1077/MessageStores.subproj/EWSConnection.m:374
    Received an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 UserInfo=0x143a245c0 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)", response: (null)
    0 Message 0x00007fff828eb119 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
    1 Message 0x00007fff828eb07e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
    2 Message 0x00007fff8282dfbe -[EWSConnection sendMessage:forRequest:] + 1117
    3 Message 0x00007fff828390ec -[EWSGateway sendMessage:forRequest:] + 79
    4 Message 0x00007fff8284bfbf -[EWSRequestOperation executeOperation] + 104
    5 Message 0x00007fff828f9347 -[MonitoredOperation main] + 229
    6 Foundation 0x00007fff878ab06d -[__NSOperationInternal start] + 681
    7 Foundation 0x00007fff878aad23 ___startOperations_block_invoke2 + 99
    8 libSystem.B.dylib 0x00007fff87dabce8 dispatch_call_block_andrelease + 15
    9 libSystem.B.dylib 0x00007fff87d8a279 dispatch_workerthread2 + 231
    10 libSystem.B.dylib 0x00007fff87d89bb8 pthreadwqthread + 353
    11 libSystem.B.dylib 0x00007fff87d89a55 start_wqthread + 13
    I'll try deleting and reinstalling the Developer Tools as hinted at in the above post, but I'm not so sure it'll make a difference for me, as my Mac Pro was immediately loaded with SL.

  • Mail attachment assertion failure Yosemite - Mail app bug

    Hi,
    I am facing a very annoying issue with Mail app. Since the upgrade to Yosemite, I am unable to save attachments with the "save all" button and the drag and drop is not working properly (sometime freezing the mail app for a minute). I am using Yosemite 10.10.2
    I tried every fix I have read online, such as :
    - rebuild mailboxes
    - repair permissions
    - remove 3 enveloppe index files in .../V2/MailData
    - reindex spotlight
    - run the command to repair permissions & reset home directory permissions and ACL (from this post : Mavericks Mail "Save Attachement..." doesn't work)
    - onyx automations...
    Nothing presented above fixed the problem.
    Here are the console logs related to the issue :
    20/02/2015 03:38:49,690 mdwrite[4655]: -[MDKeyRing initWithService:label:comment:] (/SourceCache/Spotlight/Spotlight-917.1/xpc-services/mdwrite/MDKeyRing.m:294) failed assertion -- Couldn't add Spotlight Metadata Privacy password to keychain! [osErr:-25295]
    20/02/2015 03:38:49,973 Mail[4088]: Metadata.framework [Error]: error Connection interrupted
    20/02/2015 03:38:49,973 Mail[4088]: *** Assertion failure in -[MailWebAttachment _addPrivateAttributes:], /SourceCache/Mail/Mail-2070.6/Mail/MessageDisplay/MessageView/DocumentModel/Mai lWebAttachment.m:331
    20/02/2015 03:38:49,973 Mail[4088]: [QL] Exception raised while try to get launch url for preview item: Failure in _MDItemSetPrivateAttributes: 3
    There is apparently a problem with the privacy attributes. Any idea of how to solve it?
    Thanks for your help,
    Best,
    Laurent

    Hi,
    I am facing a very annoying issue with Mail app. Since the upgrade to Yosemite, I am unable to save attachments with the "save all" button and the drag and drop is not working properly (sometime freezing the mail app for a minute). I am using Yosemite 10.10.2
    I tried every fix I have read online, such as :
    - rebuild mailboxes
    - repair permissions
    - remove 3 enveloppe index files in .../V2/MailData
    - reindex spotlight
    - run the command to repair permissions & reset home directory permissions and ACL (from this post : Mavericks Mail "Save Attachement..." doesn't work)
    - onyx automations...
    Nothing presented above fixed the problem.
    Here are the console logs related to the issue :
    20/02/2015 03:38:49,690 mdwrite[4655]: -[MDKeyRing initWithService:label:comment:] (/SourceCache/Spotlight/Spotlight-917.1/xpc-services/mdwrite/MDKeyRing.m:294) failed assertion -- Couldn't add Spotlight Metadata Privacy password to keychain! [osErr:-25295]
    20/02/2015 03:38:49,973 Mail[4088]: Metadata.framework [Error]: error Connection interrupted
    20/02/2015 03:38:49,973 Mail[4088]: *** Assertion failure in -[MailWebAttachment _addPrivateAttributes:], /SourceCache/Mail/Mail-2070.6/Mail/MessageDisplay/MessageView/DocumentModel/Mai lWebAttachment.m:331
    20/02/2015 03:38:49,973 Mail[4088]: [QL] Exception raised while try to get launch url for preview item: Failure in _MDItemSetPrivateAttributes: 3
    There is apparently a problem with the privacy attributes. Any idea of how to solve it?
    Thanks for your help,
    Best,
    Laurent

  • Db_hotbackup: assert failure

    I am investigating using Berkeley DB 4.5.20 ( with replication ) at my site.
    When I run db_hotbackup :
    db_hotbackup -h ../data/rep/ -b /tmp/dir3
    we repeatedly get the error:
    db_hotbackup: assert failure: ../db/db_dispatch.c/661: "i <= hp->generation"
    can you shed some light on to the meaning or cause of this error?
    Currently we are maintaining several DB in a single replicated environment with a daemon running updating each DB sequentially every 15 to 30 minutes.

    Hi Don,
    The internal SR number for this is: #18841 and it will be fixed. Thanks for reporting it.
    Sandra

Maybe you are looking for