Assertion:   (../lnk/exprparse.cc, line 1454) - compiler bug??

Hi,
I get the following error message:
CC -DLT_OBJDIR=\".libs/\" -I. -I. -I./include -DSOLARIS2 -DSTHREAD_CORE_PTHREAD -DARCH_LP64 -DNO_FASTNEW -DW_LARGEFILE -I/usr/local/include -xtarget=ultraT1 -m64 -features=extensions,zla -xthreadvar=no%dynamic -xdebugformat=stabs -xs -g0 -xO4 -mt -lpthread -library=stlport4 -c -o tests_simple-simple_test.o `test -f './src/tests/simple_test.cpp' || echo './'`./src/tests/simple_test.cpp
>> Assertion: (../lnk/exprparse.cc, line 1454)
while processing ./src/tests/simple_test.cpp at line 28.
The source code looks like this (tried to make a simple a possible):
---- shell.h:
class shell_t
shell_t() {}
~shell_t() {}
int start();
virtual int process()=0;
virtual int usage()=0;
--- shell.cpp:
int shell_t::start() {
...code
--- simple_test.cpp
class test_shell : public shell_t
public:
test_shell()
: shell_t()
~test_shell() {}
int process() { ...code... }
int usage() { ...code...}
int main(int argc, char* argv[])
test_sell as;
as.start();
return (0);
Has anyone seen this already?
Does somebody know, what it means, and how to fix my code?
Many thanks for all comments.
-Ippokratis.
Edited by: Ippokratis on Jun 5, 2008 11:37 PM

Any compiler assertion is a compiler bug.
If you want us to address this given issue, please, provide reproducable testcase
(e.g. exact program that fails to compile together with a command line for compilation that fails).
regards,
__Fedor.

Similar Messages

  • Compiler Error: Assertion:   (../lnk/ir_util.cc, line 344)

    Hello,
    I am getting the error : Assertion: (../lnk/ir_util.cc, line 344) when compiling with Sun C++ 5.6. Does anyone know under which circumstances this error might occur ?
    Unfortunately the sun system is not my main development environment and is only used for occasional test builds. The code that causes the error does compile under MS Windows (gcc and Visual C++)
    Therefore i can only tell that compilation was successful a while ago. I do not know if there where changes to the system nor am I able to pin the error down to a single change to my code.
    Even hints on what might cause this problem will be much appreciated.
    Thanks,
    Fr�d�ric

    All compiler assertions are due to internal consistency checks failing, meaning that something "impossible" happened from which the compiler cannot recover.
    There is no a priori way to determine what in the source code triggered the assertion. A compiler engineer needs to work with example code that results in the assertion.
    All reported assertions from ir_util.cc (one of the files that make up the C++ compiler) have been fixed in C++ 5.6 or earlier. Evidently you have found something new.
    This particular assertion means the compiler was missing internal data needed to generate debug information. Compiling without -g should eliminate the assertion. Unfortunately, your ability to debug this part of your source code would be reduced.
    If you have a support contract, you should use your support channel to report the problem. The support engineer will need sample source code that demonstrates the problem, in order to file a bug report.
    If you don't have a support contract but can narrow down a test case to something small enough to post here, I'll see what I can do. Otherwise, if you post your email address or put it in your profile, I'll let you know where you can send a larger test case.

  • Internal compiler error: Assertion: (../lnk/v2mangler.cc, line 136)

    I am working in C++ in this environment:
    $ which CC
    /hep1/lang/sunstudio11/SUNWspro/prod/bin/CC
    $ CC -V
    CC: Sun C++ 5.8 Patch 121017-10 2007/02/21
    $ uname -a
    SunOS hep 5.9 Generic_118558-37 sun4u sparc SUNW,A70
    I have run into the following internal compiler error more than once:
    >> Assertion: (../lnk/v2mangler.cc, line 136)
    while processing ./tempdir/xxx.c at line 0.
    ... where xxx.c is the preprocessed file. The error message is always the same (i.e. generated from line 136 of v2mangler.cc and complaining about line 0 of the preprocessed file). I have tried without success to isolate line(s) in my C++ source causing the error. It might help to know what the compiler is trying to do near line 136 of v2mangler.cc which triggers this error.

    This assertion prevents to mangle negative number. The source of this negative number is not clear without test case.

  • Assertion:   (../lnk/classutils.cc, line 299) - CC: Sun C++ 5.13 Beta2 2014/06/17

    The test code is
    class X
      int z : 3;
      X() : z(-1) {}
    The result is:
    vkni@solaris:~/c++$ CC -c main.cpp
    >> Assertion:   (../lnk/classutils.cc, line 299)
        while processing main.cpp at line 0.
    If I rewrite the constructor like
      X()  { z =-1; }
    it compiles without any problem.
    P.S.
    The bug is probably in the parser code, because if I forget the last ";" the first variant will fail with assertion, while the second will tell me about missing ";" like
    "main.cpp", line 7: Error: Use ";" to terminate declarations.

    Dear Fedor and Steve, thank you very much for replies. I found this problem when compiling QT4. It can be build using your compiler almost completely. Another problem, that I found, is an assertion
    >> Assertion:   (../lnk/tempparse.cc, line 3505)
        while processing ../3rdparty/javascriptcore/JavaScriptCore/API/JSCallbackObject.cpp at line 0.
    The code, that raises assertion to a very high probability is
    template <> const ClassInfo JSCallbackObject<JSObject>::info = { "CallbackObject", 0, 0, 0 };        
    template <> const ClassInfo JSCallbackObject<JSGlobalObject>::info = { "CallbackGlobalObject", 0, 0, 0     };
    (commenting both of these lines I eliminate assertion, if I leave anyone - the assertion will be raised)
    Do you know already what is that? Or I need to give you purified example?

  • Assertion:   (../lnk/storage.cc, line 99)

    Hi
    I am using the latest SunStudio11 C++ compiler
    CC: Sun C++ 5.8 Patch 121017-03 2006/07/19
    During compilation of some source files I have message:
    ">> Assertion: (../lnk/storage.cc, line 99)
    while processing ... at line 0."
    What does this message mean?
    Thanks

    It looks like you hit the compiler bug. Would you please submit it using the web interface at http://bugs.sun.com/services/bugreport/index.jsp ?
    Thanks,
    Boris

  • Assertion:   (../lnk/tmplmatchargs.cc, line 178)

    I am using studio 11 for v8 on solaris 9, with the following patches installed:
    120760-02 121015-01 121017-01 121019-01 121021-01
    When I compile the following code with "CC -c file.cpp", I get:
    >> Assertion:   (../lnk/tmplmatchargs.cc, line 178)
        while processing file.cpp at line 19.The code is:
    struct K {};
    template < class T1 , class T2 , class T3 > class A { } ;
    template < class T ,
    template < class U , class V , class W >
    class X = A >
    class B { } ;
    template < class T ,
    template < class U , class V , class W >
    class X >
    K & operator >> ( K & in , B < T , X > & P ) {
    return in ;
    typedef B < float > Z ;
    void f ( K & in , Z f ) {
        in >> f;
    }I guess it just means that it cannot deal with default values for template template arguments, but it is a violent way to say so.
    (I also got an assertion failure this morning in ../lnk/initializer.cc with an other piece of code, I will try to get my hands on it again)

    An assertion from the compiler is always a compiler bug. In this case, it looks like an internal failure in dealing with template template parameters.
    I have filed bug 6396915 for you.
    If you have a contract with Sun Service, you can track progress on fixing this bug, and get a pre-release version of the patch that fixes it.
    Otherwise, you can check the Sun Studio patch page from time to time to see whether a patch has been released that fixes the bug. A fix for this problem will not appear for at least two months.

  • Assertion:   (../lnk/ir_util.cc, line 339

    Hi ,
    Iam getting following errors
    Assertion: (../lnk/ir_util.cc, line 339)while processing myfile.cpp at line 5075.
    *** Error code 1
    The line where error is arised returned constant string which is agian
    typedef with template.
    I am using Sunstudio 8(C++ 5.5) compiler without patch.
    Also I am getting this error during release build and this file "myfile.cpp"
    compiled fine in debug mode.
    Is this compiler need any patch?
    Also this C++(5.5) that I have didn't contain any patch.
    Thanks in advance.
    -Riaj

    Please do not post the same question twice. See my answer in your original posting.

  • Assertion failed: 0, file ../lnk/exthrow.cc, line 425 Abort (core dumped)

    Hi,
    I have a JNI native library that calls a custom C++ shared library with a number of number of dependencies. At runtime, in the process of loading the custom C++ library, I got the folloing message.
    Assertion failed: 0, file ../lnk/exthrow.cc, line 425
    Abort (core dumped)
    If I did mdb on core dump, the following is the result.
    mdb java.29922
    mdb: core file data for mapping at ffb7a000 not saved: Bad address
    Loading modules: [ libc.so.1 libuutil.so.1 ld.so.1 ]
    $Cffbf7c90 libc.so.1`_lwp_kill+8(6, 0, ff2f2e10, ff2a8bd0, ffffffff, 6)
    ffbf7cf0 libc.so.1`abort+0x110(ffbf7de0, 1, 0, ad314, ff2f12d8, 0)
    ffbf7d80 libc.so.1`_assert+0x64(ff1d9358, ff1d935a, 1a9, ff1ea810, ad030, ff1d418c)
    ffbf7fe0 libCrun.so.1`__1cG__CrunMex_rethrow_q6F_v_+0xf0(0, fffb, 0, 14c14, 2, 0)
    ffbf8040 libtssclt.so.3`__1cDstdNbasic_istream4Ccn0ALchar_traits4Cc___2t6Mn0AIios_baseJEmptyCtor__v_+0xb8(eef09710, 0,
    eef0df94, eef0a088, eef09730, eef09748)
    ffbf80a0 libtssclt.so.3`__SLIP.INIT_A+0x20(0, ff2f3700, acb18, ff2bb774, f0bd4840, f0bd4880)
    ffbf8100 libtssclt.so.3`__1cU__STATIC_CONSTRUCTOR6F_v_+4(ee774a48, ff2f3700, acb18, ff1d6e50, f0bd3b40, f0bd3b80)
    ffbf8160 libtssclt.so.3`_init+0x110(ff3f40fc, ff3f5a50, 2b414, 0, ff3f4910, 821)
    ffbf81c0 ld.so.1`call_init+0x16c(c10081, 1, fe9d0f60, ee7c5eb4, ff3f4910, ffdfffff)
    ffbf8228 ld.so.1`dlmopen_intn+0x164(ff3f40fc, 10000, c01, 24, 3b, ff161f30)
    ffbf8288 ld.so.1`dlmopen_check+0x160(ff3f40fc, 10c5c8, c01, ff3914f8, ffbf834c, 0)
    ffbf82e8 ld.so.1`dlopen+0x30(10c5c8, 1, 1, ff185fac, 57c0, ff185fa8)
    ffbf8350 libjvm.so`__1cCosIdll_load6Fpkcpci_pv_+0x20(10c5c8, ffbf8858, 400, 0, 12eed4, 5400)
    ffbf83f0 libjvm.so`JVM_LoadLibrary+0x15c(10c5c8, 64fc, 38810, ff18696c, ff185fac, 2)
    ffbf8c58 libjava.so`Java_java_lang_ClassLoader_00024NativeLibrary_load+0xe8(388cc, ffbf8f2c, ffbf8f28, 0, 10c5c8, 0)
    ffbf8dc0 0xf900bc20(11, ffbf8f2c, ffbf8ea8, ffffff80, 64fc, 0)
    ffbf8e40 0xf900bbc4(f0c303c0, b6, 0, 8, 1ffc, ffbf8ec0)
    ffbf8ec0 0xf9005764(f0c30080, b8, f0c09478, f9014760, f0c374a8, ffbf8f90)
    ffbf8f58 0xf90057a8(0, b8, ffbf911c, f9014a20, 110, ffbf9028)
    ffbf9018 0xf9005764(f0c08de8, b6, ffbf919c, f9014a68, 57c0, ffbf90c0)
    ffbf90b8 0xf9005764(339b8, 0, 64fc, f9014760, ff185fac, ffbf9140)
    ffbf9140 0xf9005764(c000, 2, 4c00, f9014a70, ff17fca0, ffbf91b8)
    ffbf91b8 0xf9000218(ffbf92a0, ffbf9380, a, f4d5f2f8, f900a7e0, ffbf9390)
    ffbf9218 libjvm.so`__1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_+0x5b8(
    ffbf9378, 38810, ffbf938c, ffbf92b0, 38eb8, 0)
    ffbf92e0 libjvm.so`__1cNinstanceKlassPinitialize_impl6FnTinstanceKlassHandle_pnGThread__v_+0x68c(ffbf9524, 38810, f4d5f330,
    391cc, 38eb8, 38eb4)
    ffbf94c0 libjvm.so`__1cNinstanceKlassKinitialize6MpnGThread__v_+0x80(38e20, 38810, fecd7a8c, f4d5f330, 38810, ff181fbc)
    ffbf9540 libjvm.so`__1cbCfind_class_from_class_loader6FpnHJNIEnv__nMsymbolHandle_CnGHandle_3CpnGThread__pnH_jclass__+0xd8(
    388cc, 1, 1, 38e18, f4d5f330, 1)
    ffbf95b0 libjvm.so`jni_FindClass+0x720(388cc, 0, 0, ff18696c, 391cc, 0)
    ffbf9640 main+0xe3c(6, 388cc, ff182ba0, 39348, 0, 1)
    ffbf9ed0 _start+0x108(0, 0, 0, 0, 0, 0)
    Any help/assistance on this issue would be highly appriciated.
    Thanks and Regards
    Somesh

    I ran into this exact same problem (on Solaris, JVM 1.4.1). Although I don't know the exact cause, I can tell you what I did to fix it..
    Of course, this happens when you try to load a native library (a .so in this case). I ldd'd that .so, and found that it in turn was linked to two other libraries in my control, and some other OS libraries.
    When I statically linked either one of my libraries, such that only one of the libraries under my control was still linked dynamically, leaving the OS libaries untouched, then the problem went away. Note that it didn't matter which one I linked statically- as long as one (or both) were static there was no problem.
    My guess was that there were some sort of cyclic dependencies with these libraries, but right now I'm happy enough that it works, so I'm not going to try and pursue this further..

  • Assertion error on solarisstudio12.3 C++ compiler

    Hi
    We are moving our C++ compiler version from CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 to solarisstudio12.3 version of compiler and when we compile following C++ file using the command
    /opt/solarisstudio12.3/bin/CC -O4 -features=no%conststrings -template=no%extdef -xcode=pic32 -mt -m64 -xlibmieee -znocompstrtab -DGENERATED_BUILD_CPP -DBUILD_MODE_RO -DDM_USE_STL -DCORBA_TAO -DBITS64 -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -DSOLARIS_BITS64 -DCORBA_TAO -D_MBCS -DDLLIMPORT -D_LIB -D__MT__ -DI2_TAO_SOL -DACE_HAS_EXCEPTIONS -DSMARTHEAP -DSOLTHREADS -D__solaris -DSol210 -I. -I../utils -I../Basic -I../idls -I../Init -I../Comp -I../cont -I../../../TAO/TAO-1.5/ACE_wrappers -I../../../TAO/TAO-1.5/ACE_wrappers/TAO -I../../../TAO/TAO-1.5/ACE_wrappers/TAO/orbsvcs -I/opt/7.8-stack/SmartHeap_8.1smp/include -o expreval.o -c expreval.cpp
    Its giving assertion error
    "./errors_m.h", line 1850: Warning: Identifier expected instead of "}".
    "./wstr.h", line 278: Warning: Len hides StringExt_m::Len.
    "./any_m.h", line 25: Warning: collectionType hides Any_m::collectionType.
    "./any_m.h", line 25: Warning: multiDimData hides Any_m::multiDimData.
    "./../Comp/thread_m.h", line 89: Warning: env hides CThread_m::env.
    "./../Comp/thread_m.h", line 97: Warning: env hides CThread_m::env.
    "./allhdrs.h", line 569: Warning: Last line in file "./bit_vector.h" is not term
    inated with a newline.
    "../Comp/compinfobase.h", line 176: Warning: Name hides CompInfoBase::Name.
    "../Comp/compinfobase.h", line 181: Warning: Name hides CompInfoBase::Name.
    *>> Assertion:   (../lnk/utfutils.cc, line 79)*
    while processing mzrtpars.h at line 37._ ==>this is a LEX/YACC parser file generated by bison which has not changed since years
    When compiling the same file with our existing compiler version CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 it compiles fine with following warnings
    "/opt6/SUNWspro/bin/CC -O4 -features=no%conststrings -template=no%extdef -xcode=pic32 -mt -m64 -xlibmieee -DGENERATED_BUILD_CPP -DBUILD_MODE_RO -DDM_USE_STL -DCORBA_TAO -DBITS64 -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -DSOLARIS_BITS64 -DCORBA_TAO -D_MBCS -DDLLIMPORT -D_LIB -D__MT__ -DI2_TAO_SOL -DACE_HAS_EXCEPTIONS -DSMARTHEAP -DSOLTHREADS -D__solaris -I. -I../utils -I../Basic -I../idls -I../Init -I../Comp -I../cont -I../../../TAO/TAO-1.5/ACE_wrappers -I../../../TAO/TAO-1.5/ACE_wrappers/TAO -I../../../TAO/TAO-1.5/ACE_wrappers/TAO/orbsvcs -I/opt/7.8-stack/SmartHeap_8.1smp/include -o expreval.o -c expreval.cpp"
    "./errors_m.h", line 1850: Warning: Identifier expected instead of "}".
    "./wstr.h", line 285: Warning: Len hides StringExt_m::Len.
    "./any_m.h", line 32: Warning: collectionType hides Any_m::collectionType.
    "./any_m.h", line 32: Warning: multiDimData hides Any_m::multiDimData.
    "./../Comp/thread_m.h", line 90: Warning: env hides CThread_m::env.
    "./../Comp/thread_m.h", line 98: Warning: env hides CThread_m::env.
    "./allhdrs.h", line 569: Warning: Last line in file "./bit_vector.h" is not term
    inated with a newline.
    "../Comp/compinfobase.h", line 177: Warning: Name hides CompInfoBase::Name.
    "../Comp/compinfobase.h", line 182: Warning: Name hides CompInfoBase::Name.
    "./seqseqarr.h", line 77: Warning: chunks hides DynArr_m<SynTreeNode_m>::chunks.
    "expreval.cpp", line 1107: Where: While instantiating "SeqSeqArr_m<SynTreeNo
    de_m>::getNumUsedChunks(unsigned&) const".
    "expreval.cpp", line 1107: Where: Instantiated from non-template code.
    "./seqseqarr.h", line 77: Warning: chunks hides DynArr_m<SymTabMbr_m>::chunks.
    "expreval.cpp", line 1114: Where: While instantiating "SeqSeqArr_m<SymTabMbr
    _m>::getNumUsedChunks(unsigned&) const".
    "expreval.cpp", line 1114: Where: Instantiated from non-template code.
    11 Warning(s) detected.
    I am find of struck,any pointers please
    Thanks
    Nayeem Khan
    Edited by: 970973 on Nov 13, 2012 6:42 AM

    Hi
    I was able to find a work around for this assertion failure
    For some reason Solaris compiler was having problem parsing following Valid C++ statement
    typedef union
    Double numVal;
    UInt32 nodeInd;
    UInt32 symInd;
    UInt32 strInd;
    Bool boolVal;
    } yy_Parser_m_stype;
    So change the above statement to
    Union Parser_m_stype
    Double numVal;
    UInt32 nodeInd;
    UInt32 symInd;
    UInt32 strInd;
    Bool boolVal;
    Typedef Parser_m_stype yy_Parser_m_stype;
    This worked :-)
    Thanks for all the help

  • SQL Server Assertion: File: "logmgr.cpp" , line=5512

    Hi All,
    We are using Sql Server 2005 Express , 
    we got the below exception of Sql Server Assertion
    2014-11-17 00:26:12.59 spid51      Error: 17066, Severity: 16, State: 1.
    2014-11-17 00:26:12.59 spid51      SQL Server Assertion: File: <"logmgr.cpp">, line=5512 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning
    the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    2014-11-17 00:26:12.61 spid51      Error: 3624, Severity: 20, State: 1.
    2014-11-17 00:26:12.61 spid51      A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running
    DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. 
    2014-11-17 00:27:34.81 Server      Using 'dbghelp.dll' version '4.0.5'
    2014-11-17 00:27:34.81 Server      ***Unable to get thread context - no pss
    2014-11-17 00:27:34.81 Server      * *******************************************************************************
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * BEGIN STACK DUMP:
    2014-11-17 00:27:34.81 Server      *   11/17/14 00:27:34 spid 0
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * Non-yielding Scheduler
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * *******************************************************************************
    2014-11-17 00:27:34.81 Server      Stack Signature for the dump is 0x000003E6
    2014-11-17 00:27:35.75 Server      External dump process return code 0x20000001.
    External dump process returned no errors.
    2014-11-17 00:27:35.75 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    99%. Interval: 75000 ms.
    2014-11-17 00:28:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 135953 ms.
    2014-11-17 00:29:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 195953 ms.
    2014-11-17 00:30:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 255953 ms.
    2014-11-17 00:31:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 315953 ms.
    2014-11-17 00:32:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 375953 ms.
    2014-11-17 00:33:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 435953 ms.
    2014-11-17 00:34:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 495953 ms.
    2014-11-17 00:35:05.77 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2014-11-17 00:35:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 555953 ms.
    2014-11-17 00:36:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    97%. Interval: 615953 ms.
    2014-11-17 00:37:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 675953 ms.

    Assertion error are usually some corruption in SQL Server database. And non yielding scheduler seems like bug what is output of
    select @@Version
    Did you tried running dbcc checkdb on SQL Server 2005 database
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Foreach syntax + generics, Possible compiler bug?

    I'm encountering an odd problem trying to use generics and the foreach (colon) syntax. The code in question:
    for (Iterator<String> it = col.getParameterNames().iterator(); it.hasNext();) {}
    for (String paramName : col.getParameterNames()) {}col is an instance of an inner class of the class whose method this code snippet is from, getParameterNames has the signature:
    public Set<String> getParameterNames();
    The first line, using the Iterator<String> explicitly, compiles fine. The second line, when present, raises the compiler error:
    found : java.lang.Object
    required: java.lang.String
    for (String paramName : col.getParameterNames()) {
    I cannot seem to reliably reproduce this situation in other (simpler) classes I write, but this one in particular seems to trigger it. Is it possible this is a compiler bug, or might there be something I'm doing incorrectly that I'm missing? Are my expectations about how the second line should work incorrect? It seems to in other circumstances...
    javac is 1.6.0_01. Any ideas?

    Here is a quick update, I'm more inclined to think of this as bad behavior now.
    This code compiles:
    public class Test {
    Vector<InnerTest> inners = new Vector<InnerTest>();
        public class InnerTest {        
           public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
        public Test() {
            for (InnerTest it : inners) {
                for (String s : it.someSet()) {        
    }however, the following does not:
    public class Test {
    Vector<InnerTest> inners = new Vector<InnerTest>();
        public class InnerTest<P> {        
           public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
        public Test() {
            for (InnerTest it : inners) {
                for (String s : it.someSet()) {        
    }Again, the problem might be with my expectations (I haven't gone through the specifications yet with this in mind), but I can't fathom how or why the unused parameter would make a difference in that method's tpye matching.

  • Another Compiler Bug (message: An internal build error has occurred... Unknown Flex Problem)

    I was fighting with this problem for a few days. Finally I've got it resolved. I want to describe it and fill in BUG in the bug report, but I am not sure about Adobe support options. So, I am putting bug report here.
    1. ASSUMPTION: All problems which compiler reports as unknown problem are the real compiler BUGs/Problems. Eventually MXML compiler/ActionScript compiler should be able to take C++ or FORTRAN code or an aribitrary text and nicely tell "Error: It is not ActionScript (Flex) code" or "the code is corrupted from Line so and so...". When compiler crashed, it is most probably due to one of the states not handled (or not handled correct). Keeping this in mind I assume, that my code has nothing to do with the compiler crash.
    2. PROBLEM Description.
         - I tried to port our internal project from Flex3.5/Flex Builder 3 to Flex4.1/Flash Builder 4.
         - After checking out and trying to build code I start getting weird problems like Error 1037: Packages cannot be nested.
         - After cleaning and compiling project by project, walking up dependency tree, I was able to get rid of this problem.
         - On last Project I've got another problem (An internal build error has occurred... Unknown Flex Problem). Which I stuck with for a while.
         - When I checked log file I found following messages:
    ============================================================
    !ENTRY com.adobe.flexbuilder.project 4 43 2010-12-21 15:45:24.353
    !MESSAGE Uncaught exception in compiler
    !STACK 0
    java.lang.ClassCastException: macromedia.asc.parser.InputBuffer cannot be cast to flex2.compiler.as3.CodeFragmentsInputBuffer
    at flex2.compiler.as3.AbstractSyntaxTreeUtil.lineNumberToPosition(AbstractSyntaxTreeUtil.jav a:1266)
    at flex2.compiler.mxml.ImplementationGenerator.generateBinding(ImplementationGenerator.java: 569)
    at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetupFunction(ImplementationG enerator.java:863)
    at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetup(ImplementationGenerator .java:812)
    at flex2.compiler.mxml.ImplementationGenerator.generateInitializerSupportDefs(Implementation Generator.java:1878)
    at flex2.compiler.mxml.ImplementationGenerator.generateClassDefinition(ImplementationGenerat or.java:1044)
    at flex2.compiler.mxml.ImplementationGenerator.<init>(ImplementationGenerator.java:206)
    at flex2.compiler.mxml.ImplementationCompiler.generateImplementationAST(ImplementationCompil er.java:499)
    at flex2.compiler.mxml.ImplementationCompiler.parse1(ImplementationCompiler.java:197)
    at flex2.compiler.mxml.MxmlCompiler.parse1(MxmlCompiler.java:168)
    at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2871)
    at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2824)
    at flex2.compiler.CompilerAPI.batch2(CompilerAPI.java:446)
    at flex2.compiler.CompilerAPI.batch(CompilerAPI.java:1274)
    at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1496)
    at flex2.tools.oem.Application.compile(Application.java:1188)
    at flex2.tools.oem.Application.recompile(Application.java:1133)
    at flex2.tools.oem.Application.compile(Application.java:819)
    at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:344)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(A SApplicationBuilder.java:276)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplication Builder.java:127)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:190)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:7 4)
    at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectB uilder.java:480)
    at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuild er.java:306)
    at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncremen talBuilder.java:157)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
    at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516)
    at org.eclipse.core.internal.resources.Project.build(Project.java:94)
    at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:221)
    at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162)
    at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38 )
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    !SESSION 2010-12-22 09:48:27.766 -----------------------------------------------
    eclipse.buildId=M20100909-0800
    java.version=1.6.0_16
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Framework arguments:  -product org.eclipse.epp.package.jee.product
    Command-line arguments:  -data C:\Client_Flex4 -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
    ================================================
    3. RESOLUTION/WORK AROUND
         - I was able to get this problem cleared by putting compiler option for Flex Application projects:  -keep-generated-actionscript
    4. SIDE NOTE
      I do not really see putting this compiler option as the solution and living with the mistery is making me fill a bit bad.

    Hi Faser,
    I just tried it on Vista with our latest FB Plugin build but
    I was unable to reproduce your issue with the following setup:
    - FB Plugin build installed by Administrator account user
    under her Documents folder
    - Administrator account user can launch, create Flex projects
    under her own workspace without any problems
    - Standard account user can launch the FB Plugin build (need
    Admin's password) and create Flex project (default location) under
    his own workspace
    If your setup is different, can you please log a bug at
    http://bugs.adobe.com/flex.
    Be sure to include what build you are using, whether it's
    reproducible, the detail of the setup, etc...
    thanks,
    Sharon

  • SS9 CC5.6 compiler bug - algorithm count confused with struct member

    Found some code that fails to compile in CC 5.6
    CC: Sun C++ 5.6 2004/07/15
    #include <algorithm>
    using namespace std;
    struct A {
      int count;   
    struct B
      struct A *a;
    int main(int argc, char **argv)
      struct B *b = 0;
      // This line fails to build, any other operator is ok
      if ( b->a->count < 50 )
      return (1);
    }Fails with error :
    "c56_algorithm_bug.cpp", line 21: Error: Unexpected ")" -- Check for matching parenthesis.
    "c56_algorithm_bug.cpp", line 22: Error: "," expected instead of "{".
    "c56_algorithm_bug.cpp", line 22: Error: Illegal value for template parameter.
    "c56_algorithm_bug.cpp", line 22: Error: ")" expected instead of "{".
    4 Error(s) detected.The compiler is getting confused with the use of the count struct member vs the count algorithm. Changing the < to a > fixes the problem.
    Using CC5.3 works fine as well as all other compilers we use (gcc 3.4, mipspro 7.4, VC 7.1)
    Anyone seen this ?
    - mark

    This bug has been fixed in the C++ 5.6 compiler. I'm not sure if the fix is in the first patch which is about to be released. If not, the fix definitely will be in the next patch.
    The workaround is not to use
    using namespace std;That using-declaration is a pretty big hammer, and often results in conflicts with user code, compiler bugs aside.

  • Local class and switch statement -- compiler bug?

    Does anybody know why the following does not compile with "LocalClass cannot be resolved to a type" error in the case 1: block
    public class ProblemClass {
         public void localClassProblem() {
                   class LocalClass {
                        void doNothing() {};          
                   int i = 0; 
                   switch (i) {                    
                        case 1: {
                             LocalClass instance1 = new LocalClass();  //ERROR: unresolved type
                                            break;
    }while the following does (I only added case 2: where LocalClass type is not referenced within an embedded block)
    public class ProblemClass {
         public void localClassProblem() {
                   class LocalClass {
                        void doNothing() {};          
                   int i = 0; 
                   switch (i) {                    
                        case 1: {
                             LocalClass instance1 = new LocalClass();
                                            break;
                        case 2:
                             LocalClass instance2 = new LocalClass();
    }Is it a compiler bug? Thanks for clarifying this.
    --Michal                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    I'm using 1.5.0-b64
    --Michal                                                                                                                                                                                                                                   

  • Strange compiler bug in method overloading mechanism

    Hi,
    current javac compiler in version 1.4.2_10 and probably earlier versions seem to have a bug in the overloading mechanism of static methods in a certain case.
    I consider reporting this as a compiler bug but would like to have some feedback before.
    Would you consider this class correct? With 5+ years of java experience I'd consider it being correct:
    package test;
    public abstract class AbstractClass {
       public class RealizationClass extends AbstractClass {
          public void someMethod() {
             m(1); //Error: m(int,int) in test.AbstractClass cannot be applied to (int)
             m(1, 2);
       private static int m(int i) {
          return i+1;
       private static int m(int i, int j) {
          return i+j;
    }Interestingly the order of those two static method and their visibility affects the error (changing visibilty to public/protected makes javac accept the code).
    Eclipses compiler does not have this problem, it happily accepts the code above.
    What do you think?
    -Sebastian

    JLS 2.0 says on page 147: "The scope of a declaration of a member m declared in or inherited by a class type C is the entire body of C, including any nested type declarations."
    I read somewhere that in the case a nested or inner class accesses private fields of its enclosing type, the compiler generates "sythetic accessor methods" to allow access. Maybe there's something wrong with the generation of these generated methods...

Maybe you are looking for

  • How to get serch-adminauditlogs in simple english

    how to get serch-adminauditlogs in simple english Is it possible to conver to Event-logs or any text files with simple english Raj

  • MEncoder: DVD to avi with subtitles results in screen flicker

    I'm trying to make an avi-file using mencoder with subtitles. Playing the DVD, or the VOB-file in mplayer works and encoding it without subs in mencoder works, but as soon as I include the subs, the avi-movie starts to flicker like crazy after the fi

  • Mac slideshow capabilities in Premier Elements 11

    In Premiere Elements 11, does the Mac version have the same slideshow capabilities as the Windows version? If not, how do they differ? Howard

  • Install webdb in 8i at solaris, pls help!!!!

    This is the fifth time I failed in installing webdb in 8i at solaris 2.7. The problem is: when I go to the webdb home, I got an ora-06564 :object gateway.home does not exist. I guess probably because I installed webdb in the ORACLE_HOME, but the weir

  • CORBA communication trouble - BAD_PARAM?

    Being into learning how to use CORBA with Java, I'm following the trail through the Java IDL tutorial to be found at http://java.sun.com/j2se/1.4.2/docs/guide/idl/GShome.html This is what I did so far: - an orbd is running at localhost, port 1050. -