Signal in solaris 10

Are the signals in solaris 10 are per process ? ??
would like to know wether the setitimer in solaris 10 is per process or per thread.
Please reply for this query

Hope it gives you some clue:
http://docs.sun.com/app/docs/doc/816-5137/6mba5vpju?a=view#gen-10856

Similar Messages

  • Can I catch ALRM signal on solaris ?Urgent......

    Hi !
    Is it possible to catch the ALRM signal on Solaris ?? I heard that trying to catch a signal that will be handled by the JVM will throw an IllegalArgumentException. This is what happening when I try to catch the ALRM signal. I'm getting "java.lang.IllegalArgumentException : UnknownSignal : ALRM". But, in the same application, I'm able to catch INT and TERM signals.Can anyone tell me how to trap the ALRM signal on Solaris ???
    Thanks in advance .
    Ramesh Thota

    No ! I did not use any native code. I've used the classes sun.misc.Signal and sun.misc.SignalHandler for this. Here is my code :
    import sun.misc.Signal;
    import sun.misc.SignalHandler;
    public class test implements Runnable
    public static boolean signalFlag = false;
    public static Object valueLock = new Object();
    public static void main(String args[])
    test t = new test();
    Thread thread = new Thread(t);
    thread.start();
    String SIG_TERM = "TERM";
    String SIG_INT = "INT";
    String SIG_ALRM = "ALRM";
    SignalHandler sigHdl = new SignalHandler ()
         public void handle( Signal aSignal )
         synchronized(valueLock)
              signalFlag = true;
              System.out.println( "Caught " + aSignal.toString()+ " signal.");
              System.out.println(signalFlag);
              valueLock.notify();
         } // End of Sync Block
    } // End of method handle
    }; //end of class
    // Installing signal handlers
    Signal.handle( new Signal( SIG_INT ), sigHdl );
    Signal.handle( new Signal( SIG_TERM ), sigHdl );
    Signal.handle( new Signal( SIG_ALRM ), sigHdl );
    } // End of Main
    public void run()
    try{
         synchronized(valueLock)
         while(signalFlag != true)
         valueLock.wait();
    } // end of try
    catch(InterruptedException iox)
         System.out.println("Interrupted");
    } // End of Run
    }// End of Class

  • Forte's benchmark

    Hi,
    I'm looking for some benckmarks of Forte architecture
    on 2-tier and 3-tier C/S.
    And where can I find articles or whitepapers about
    load balancing and transactional locking in Forte.
    Many thanks
    Herve
    DO YOU YAHOO!?
    Get your free @yahoo.com address at http://mail.yahoo.com

    George,
    I'm rusty with Forte and I'm not sure about signals on Solaris
    but the mention of threads on Solaris brought to mind a couple
    points that you should know. This was true as far as I can
    tell in 3.0.E.0 on Solaris 2.6.
    1. By default in interpreted partitions FTEXEC does not use
    solaris threads, it uses Forte threads. You must tell it
    to use DCE threads.
    Once you're in the partition workshop you can bring up the
    partition properties for the server partition that you want
    Sun threads for. In the properties dialog there is an option
    called "Thread Package". If you choose DCE then it'll use
    Sun threads.
    2. Compiled partitions require yet another trick.
    You must add the flag "-tlpt" which I believe stands
    for "thread library posix threads", meaning DCE threads,
    meaning native threads.
    Turn on trace flag "trc:os:14" on your Solaris box before
    starting up the compiled partiton. This will show all
    the shared libraries getting loaded into the partition.
    install/lib/libqqptli.so is the posix thread library.
    Regards, and good luck.
    [email protected]
    Hi there,
    Could somebody please tell me which signals does Forte use to
    schedule thread-switching on Solaris 2.5? or does Forte catch
    the following two signals, SIGSEGV and SIGBUS?
    Thanks a lot.
    George
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>------------------------------------------------------------------------
    Any views expressed in this message are those of the individual sender,
    except where the sender specifically states them to be the views of
    Reuters Ltd.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • Pls Help - Unexpected Signal 11 occuring on solaris 8

    Hi,
    We are getting Unexpected Signal 11 crashes on solaris 8 our Application server is crashing with following core dump msg
    Unexpected Signal : 11 occurred at PC=0xFE455CF4
    Function=[Unknown. Nearest: JVM_GetInterfaceVersion+0xE0]
    Library=/u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/libjvm.so
    Dynamic libraries:
    0x10000      /user2/epoint/pups
    0xff080000      .//libxalan-c1_2.so
    0xfed80000      .//libxerces-c1_6_0.so
    0xff050000      /usr/lib/libsocket.so.1
    0xfec80000      /usr/lib/libnsl.so.1
    0xfed60000      /usr/lib/libpthread.so.1
    0xfed40000      /usr/lib/librt.so.1
    0xff3a0000      /usr/lib/libdl.so.1
    0xfec50000      /usr/lib/libCrun.so.1
    0xfec00000      /usr/lib/libm.so.1
    0xff040000      /usr/lib/libw.so.1
    0xfebc0000      /usr/lib/lwp/libthread.so.1
    0xfea80000      /usr/lib/libc.so.1
    0xfeb90000      /usr/lib/libgen.so.1
    0xfeb70000      /usr/lib/libmp.so.2
    0xfea60000      /usr/lib/libaio.so.1
    0xfebf0000      /usr/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1
    0xfe8c0000      /user2/epoint/pjni.dll
    0xfe400000      /u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/libjvm.so
    0xfe890000      /u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/native_threads/libhpi.so
    0xfe860000      /u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/libverify.so
    0xfe3c0000      /u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/libjava.so
    0xfe3a0000      /u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/libzip.so
    0xfa7a0000      /u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/libnet.so
    0xfa6e0000      /u02/iplanet6.1/j2sdk1.4.1/jre/lib/sparc/librmi.so
    0xfa6c0000      /user2/epoint/pcom.dll
    0xfa690000      /user2/epoint/psl.dll
    0xfa5c0000      /user2/epoint/pfile.dll
    0xfa590000      /user2/epoint/psysapi.dll
    0xfa4e0000      /user2/epoint/pdll.dll
    0xfa4b0000      /user2/epoint/pxml.dll
    0xf1ab0000      /user2/epoint/pactions.dll
    0xf1590000      /user2/epoint/pcti.dll
    0xf13e0000      /user2/epoint/psocket.dll
    0xf0cb0000      /user2/epoint/psqldb.dll
    0xf0da0000      /user2/epoint/poracle.dll
    0xea800000      /export/home/oraep/oracle8/lib/libclntsh.so.8.0
    0xf0c90000      /export/home/oraep/oracle8/lib/libwtc8.so
    0xf0be0000      /usr/lib/libsched.so.1
    Local Time = Thu Feb 3 17:58:24 2005
    Elapsed Time = 216
    # HotSpot Virtual Machine Error : 11
    # Error ID : 4F530E43505002E6 01
    # Please report this error at
    # http://java.sun.com/cgi-bin/bugreport.cgi
    # Java VM: Java HotSpot(TM) Client VM (1.4.1-b21 mixed mode)
    Details of Environemnt :-
    OS :- Solaris 8
    Webserver :- Sunone 6.1 SP3 with JDK 1.4.1
    Application Server (developed in C++ and make native calls with java using JNI ) uses JDK 1.3.1_09
    DB:- Oracle 8.1.7.4
    Is this a JDK Bug ? Should we upgrade JDK
    Also we are using 2 diff JDK versions Sunone on JDK1.4.1 while our Application server is on JDK 1.3.1_09 can this be a cause ???
    Please help me to resolve the problem

    Hi, you can find some answers here: http://www.bitwizard.nl/sig11/.
    Using this article you can detect if it is a hwd problem or a sofware one
    good luck

  • Signals in Multithreaded Application on Solaris 10.

    HI All,
    I need to know are the signal handlers are inherited by threads.
    Assume I have defined a signal handler (assume for SIGCHLD )in main function before the creation of threads, and after that I create 5 threads. Can anyone please tell me if the signal SIGCHLD comes to any of the 5 threads will it be handled as signal handler defined earlier.
    Any comments will be appreciated.
    Regards,
    Rahul.

    What do you mean by 'linux application'? Right now, you'd have to recompile the program from source on Solaris or install a precompiled Solaris package.
    After the release of project Janus, you might have some other choices to run Linux binaries directly on a Solaris (x86) machine.
    Darren

  • Solaris Studio 12.4 ccfe signal 11 with boost::unordered_set in C  11 mode

    Using Solaris Studio 12.4 on Solaris 10 update 10 x86, the following program crashes ccfe:
    #include <boost/unordered_set.hpp>
    #include <string>
    int main(int, char **)
        boost::unordered_set<std::string> strSet;
        std::string str("test");
        strSet.insert(str);
        return 0;
    Assuming the code is saved to main.cc, build it in C++11 mode using:
    CC -v -std=c++11 -m64 -I/usr/local/include/boost-1_54 main.cc
    The output is:
    ### CC: Note: NLSPATH = /opt/solarisstudio12.4/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/solarisstudio12.4/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
    ###     command line files and options (expanded):
    ### -v -std=c++11 -m64 -I/usr/local/include/boost-1_54 main.cc
    /opt/solarisstudio12.4/lib/compilers/ccfe -xarch=amd64 -std=c++11 -D__SunOS_5_10 -D__SUNPRO_CC=0x5130 -D__unix -D__SVR4 -D__sun -D__SunOS "-D__builtin_expect(e,x)=e" -D__x86_64 -D__x86_64__ -D__amd64 -D__amd64__ -D_LP64 -D__LP64__ -D__BUILTIN_VA_STRUCT -Dunix -Dsun -D__SUN_PREFETCH -D__SUNPRO_CC_COMPAT='G' -include /opt/solarisstudio12.4/lib/compilers/include/CC/gnu/builtins.h -include /opt/solarisstudio12.4/lib/compilers/include/CC/gnu/builtins-def.h -I/usr/local/include/boost-1_54 -I-xbuiltin -I/opt/solarisstudio12.4/lib/compilers/include/CC/gnu -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/include/c++/4.8.2/ -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/include/c++/4.8.2//backward -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/include/c++/4.8.2/i386-sun-solaris2.10/amd64/ -I/opt/solarisstudio12.4/lib/compilers/include/cc -I/usr/include -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/lib/gcc/i386-sun-solaris2.10/4.8.2/include// -ptf /tmp/ccfe.1422033660.29374.03.%1.%2 -ptx /opt/solarisstudio12.4/bin/CC -ptk "-v -std=c++11 -m64 -I/usr/local/include/boost-1_54 " -compat=g -xdebuginfo=%none -xdbggen=dwarf+usedonly+incl -xF=%none -xbuiltin=%none -xldscope=global -xivdep=loop -O0 -xarrayloc main.cc -o /tmp/ccfe.1422033660.29374.01.ir 2> /tmp/ccfe.1422033660.29374.02.err
    /opt/solarisstudio12.4/lib/compilers/stdlibfilt -stderr < /tmp/ccfe.1422033660.29374.02.err
    >> Signal 11:
        while processing main.cc at line 0.
    rm /tmp/ccfe.1422033660.29374.02.err
    rm /tmp/ccfe.1422033660.29374.01.ir
    I know Boost 1.54 is not the most recent version, but the only changes to unordered_set.hpp between 1.54 and the current master branch in Boost's Git repository are Visual Studio 2013 workarounds, so I strongly suspect the same problem would occur with Solaris Studio 12.4 and more recent versions of Boost.
    This problem can be avoided by using std::unordered_set instead of boost::unordered_set.  However, since the compiler actually suffers a SEGV rather than giving a nice error message I thought I'd report this in case it's a sign of a problem in the compiler that might occur under other circumstances too.

    Thanks for the help.  Yes, sorry, I should have made clear that this is after trying to use Boost in C++11 mode.  I agree that the problem doesn't occur when using Solaris Studio in C++11 mode but Boost configured not to use any C++11 features.
    I made quite a few edits to the Boost code, including the ones Steve posted in this thread.  The edit that causes this problem to occur is the one to boost/config/compiler/sunpro_cc.hpp that removes all the BOOST_NO_CXX11_* macros.
    It sounds like I should just hold off trying to use Boost in C++11 mode until the next version of Solaris Studio is out.
    The pstack from the ccfe core dump is:
    core 'core.1503' of 1503:       /opt/solarisstudio12.4/lib/compilers/ccfe -xarch=amd64 -std=c++11 -D__
    ffff0000 ???????? (8041218, 8, fcf58e0, 0)
    082b7713 __1cPtemp_name_substKsubstitute6MrknQfull_syntax_name__1_ (8041260, 8041180) + 163
    082be63d __1cKexpr_substKvisit_name6MpnJname_expr__v_ (80413c0, ad65da8, 8041348, 8275d73) + fd
    082bc775 __1cKexpr_substKsubstitute6MpknEexpr__p1_ (80413c0, f2cab18, 80413a8) + 35
    082b858b __1cPtemp_name_substQsubst_single_arg6MnPtemplate_actual__k1_ (80415d0, 8041b10, f2cab18, 103, 8041570, 0) + 2fb
    082b8e10 __1cPtemp_name_substUsubstitute_temp_args6MrknbBtemplate_actuals_collection_pknXtemplate_parameter_list__1_ (8041890, 8041b10) + 150
    082ba050 __1cPtemp_name_substPvisit_temp_args6MrknbJsyntax_name_with_template_arguments__v_ (8041b10, fc9dd80, 8041ac0, 8041964) + 30
    082ba2c8 __1cPtemp_name_substFvisit6MrknQsyntax_name_impl4eInSsyntax_name_sort_t____v_ (8041b10, fc9dd80, fcf5610, 0) + 18
    082b76d1 __1cPtemp_name_substKsubstitute6MrknQfull_syntax_name__1_ (8041bf0, 8041b10) + 121
    082b526b __1cPtemp_type_substUvisit_name_dependent6MpnEtype_pnTname_dependent_type__v_ (8041eb0, f2e1aa4, f2e1a58, f2e21f0) + 5b
    082b3930 __1cPtemp_type_substTsubstitute_ret_type6MpnJfunc_type__pnEtype__ (8041eb0, f2e2178, 8041d08, 8041d60) + 30
    082b3c2c __1cPtemp_type_substKvisit_func6MpnEtype_pnJfunc_type__v_ (8041eb0, f2e21a0, f2e2178, f2e21f0) + 25c
    082ba941 __1cPtemp_type_substTexpand_in_func_type6MpnJfunc_type__2_ (8041eb0) + 31
    0816b754 __1cIfunc_symRnew_template_spec6kMrknbBtemplate_actuals_collection_rknIposition__pnDsym__ (f2e21f0) + c4
    082c941b __1cQtemplate_matcherIgen_func6M_pnIfunc_sym__ (8042050, ad62d58, ad65960, 0) + 59b
    0828af3f ???????? (80420f4, ad65940, 80421a0, 0, ad62c50, 0)
    0828b2c9 __1cNoverload_call6FpnJcall_expr_rknJsym_array_4brknbBtemplate_actuals_collection_nEtypeKtype_class_b_2_ (8042198, ad65940, 804219c, 80421a0, 0, ad62c50) + 99
    08204c38 ???????? (ad65940)
    082086ff __1cLtypify_call6FpnJcall_expr_I_pnEexpr__ (ad65940, 4, 0, fd33148) + 9bf
    081e36a5 __1cXtypify_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8042530, ad65940, 0, 0) + 15
    081e4529 __1cGtypify6FpnEexpr_I_1_ (ad65940, 4, 0, 0) + c9
    082b1e0a __1cJexpr_stmtOpass_thru_expr6MpnEexprHvisitor__v_ (ad659a0, 80425b0, 0, 83bb23e) + 1a
    081e3cd1 __1cXtypify_dispatch_visitorPvisit_statement6MpnOstatement_expr__v_ (8042660, ad62b28, 8042608, 83bbbe9) + 71
    081e4529 __1cGtypify6FpnEexpr_I_1_ (ad62b28, 0, 8759ec0, fc9b740) + c9
    08266956 __1cWstore_inline_func_body6FpnIfunc_sym_pnFscope_bb_pnEexpr__ (fd2fc80, fc9b740, 1, 1) + 426
    082700c8 __1cSinline_bookkeepingOprocess_inline6MpnIfunc_sym_pnJcall_expr_pnEexpr__6_ (8d61508) + 268
    08270542 __1cSinline_bookkeepingNexpand_inline6MpnJcall_expr_pnEexpr__4_ (8d61508, ad5ecf8, 87594a8, 0) + f2
    081e10e3 ???????? (ad5ecf8, 80005, 8043208, 85a44ab)
    081d673e __1cWbind2_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8043220, ad5ecf8, fd1e6b8, fcb9a40) + 9e
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad5ecf8, 80005, 8043288, 0) + a2
    082a94e7 ???????? (ad5ecf8, 0, 0, 0)
    082aaaf3 __1cRstmt_bind_visitorKvisit_expr6MpnJexpr_stmt__v_ (8043350, ad5ed58, 80432f8, 804337c) + 93
    082a8f2f __1cRstmt_bind_visitorOstmt_list_bind6MpnJstatement__2_ (8043350, ad5ed58, 2211, 7fefefef) + 8f
    082b06b5 __1cRstmt_bind_visitorPvisit_statement6MpnOstatement_expr__v_ (8043350) + b5
    082a9294 __1cJstmt_bind6FpnOstatement_expr_b_v_ (ad5bef0) + b4
    081df9c6 ???????? (ad5bef0, 0, 8043428, 8272a37)
    081d6e18 __1cWbind2_dispatch_visitorPvisit_statement6MpnOstatement_expr__v_ (8043420, ad5bef0, 8043448, 8043494) + 98
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad5bef0, 0, 8043488, 81710d5) + a2
    082726f0 __1cSinline_bookkeepingQfinish_expansion6MrnbDfunction_definition_interface_pnEexpr__4_ (8d61508, fd2b46c, ad5bef0, 0) + 160
    081e10f9 ???????? (ad4b210, 80005, 8043528, 82759da)
    081d673e __1cWbind2_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8043520, ad4b210, 0, fcb9a40) + 9e
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad4b210, 80005, 8043578, ad55cc0) + a2
    082a94e7 ???????? (ad4b210, 0, 0, 0)
    082aaaf3 __1cRstmt_bind_visitorKvisit_expr6MpnJexpr_stmt__v_ (8043650, ad4b270, fd1e668, 874cef8) + 93
    082a8f2f __1cRstmt_bind_visitorOstmt_list_bind6MpnJstatement__2_ (8043650, ad4a7b0, 1, 7fefefef) + 8f
    082b06b5 __1cRstmt_bind_visitorPvisit_statement6MpnOstatement_expr__v_ (8043650) + b5
    082a9294 __1cJstmt_bind6FpnOstatement_expr_b_v_ (ad4a520) + b4
    081d6e18 __1cWbind2_dispatch_visitorPvisit_statement6MpnOstatement_expr__v_ (8043720, ad4a520, 8043748, 8043794) + 98
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad4a520, 0, 8043788, 81710d5) + a2
    082726f0 __1cSinline_bookkeepingQfinish_expansion6MrnbDfunction_definition_interface_pnEexpr__4_ (8d61508, fc7b144, ad4a520, 0) + 160
    081e10f9 ???????? (ad035e8, 80005, fd1e368, 85a4400)
    081d673e __1cWbind2_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8043820, ad035e8, acffdb8, fcb9a40) + 9e
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad035e8, 80005, 8043878, 0) + a2
    082a94e7 ???????? (ad035e8, 0, 0, 0)
    082aaaf3 __1cRstmt_bind_visitorKvisit_expr6MpnJexpr_stmt__v_ (80439c0, ad03648, ad03668, 8759ec0) + 93
    082a8f2f __1cRstmt_bind_visitorOstmt_list_bind6MpnJstatement__2_ (80439c0, acf9468, 0, 82d7323) + 8f
    082afb6b __1cRstmt_bind_visitorWvisit_function_variant6MpnNfunction_stmt_b_v_ (80439c0, ad04358, 1, 8043a30) + 46b
    082afe10 __1cRstmt_bind_visitorOvisit_function6MpnNfunction_stmt__v_ (80439c0, ad04358, ad04378, 8759ec0) + 40
    082a916f __1cUstmt_bind_and_expand6FpnJstatement__1_ (ad04358, 3, fc55f4b, 80443c4) + 11f
    08257545 __1cMfunc_contextJpostamble6MrnbDfunction_definition_interface_pnNfunction_stmt__v_ (871cc98) + d5
    082e879d __1cTimmediate_func_body6FpnIfunc_sym__v_ (fbd3840, fbd3390, 8044dd0, 821b71f) + 3fd
    08266428 __1cMparse_inline6FrnbDfunction_definition_interface__v_ (fbd385c, fbd38cc, 8044eb0, 95a38d4) + 188
    084db8c8 __1cLemit_inline6FpnIsym_list__v_ (fca5328, fca5328) + 2d8
    084d88f1 __1cQcompilation_unitFclean6M_b_ (8759310) + a1
    084dd507 __1cIfinalgen6F_v_ (8c3ffa8, 8759178, 8046eb8, 815db68, 1, 8c41eb8) + 67
    082f533b __1cGanalys6Fb_v_ (1, 8c41eb8, 8046eb8, 815d5d7) + db
    0815db68 __1cHtmcplus6Fri0bpnHoptions__nHsym_set__ (8046f00, 8046ef8, 8046efc, 1, 8c4ced8, 86417b1) + 2be8
    082e5943 main     (34, 8047360, 8047434) + 283
    08153f22 _start   (34, 8047514, 804753e, 804754b, 8047556, 8047565) + 72

  • Core Dump on Solaris 10 (Signal 10 - Bus Error), but not on Solaris 8?

    Hi,
    We just moved our product from Solaris 8 to Solaris 10. It runs for months on Solaris 8 without any problems, while core dumped after running about 2 weeks on Solaris 10.
    Any clue on what could be wrong is apprecaited.
    pam

    Hi Andrew,
    Appreciate your answer very much. I am very new to Solaris and UNIX in general. Would you please let me know what kind of info would help diagnose the
    problem? I have stack pointer, output of "where" from gdb. frme pointer, etc.
    pam
    ===================
    GNU gdb 6.3
    Copyright 2004 Free Software Foundation, Inc.
    GDB is free software, covered by the GNU General Public License, and you are
    welcome to change it and/or distribute copies of it under certain conditions.
    Type "show copying" to see the conditions.
    There is absolutely no warranty for GDB. Type "show warranty" for details.
    This GDB was configured as "sparc-sun-solaris2.8"...(no debugging symbols found)
    Core was generated by `./warnsrvr'.
    Program terminated with signal 10, Bus error.
    #0 0x001a3ca8 in __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__ ()
    (gdb) where
    #0 0x001a3ca8 in __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__ ()
    #1 0x001a3ca8 in __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__ ()
    Previous frame identical to this frame (corrupt stack?)
    ======================================
    (gdb) disassemble 0x001a3ca8
    Dump of assembler code for function __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__:
    0x001a3c24 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+0>: cmp %o0, 1
    0x001a3c28 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+4>: be,pn %icc, 0x1a3c38 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+20>
    0x001a3c2c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+8>: sethi %hi(0x572000), %l6
    0x001a3c30 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+12>: ret
    0x001a3c34 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+16>: restore %g0, 0, %o0
    0x001a3c38 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+20>: ld [ %l6 + 0x358 ], %l5
    0x001a3c3c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+24>: cmp %l5, 0
    0x001a3c40 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+28>: bne,pn %icc, 0x1a3c50 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+44>
    0x001a3c44 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+32>: cmp %l5, 1
    0x001a3c48 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+36>: ret
    0x001a3c4c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+40>: restore %g0, 1, %o0
    0x001a3c50 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+44>: bne,pn %icc, 0x1a3cb0 <__1cSWPReferenceManagerOInputIonoModel6MrknKIONO_MODEL_khki_nGRESULT__+4>
    0x001a3c54 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+48>: sethi %hi(0x1a3c00), %l7
    0x001a3c58 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+52>: mov -1, %i1
    0x001a3c5c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+56>: sth %i1, [ %fp + -1864 ]
    0x001a3c60 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+60>: add %fp, -1824, %o0
    0x001a3c64 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+64>: ldd [ %l7 + 8 ], %f0
    0x001a3c68 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+68>: call 0x1c87f0 <___const_seg_900001301+16>
    0x001a3c6c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+72>: std %f0, [ %fp + -1856 ]
    0x001a3c70 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+76>: call 0x1cf888 <__1cKIono2Ascii6FrknKIONO_MODEL_pcki_v_+100>
    0x001a3c74 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+80>: add %fp, -1864, %o0
    0x001a3c78 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+84>: sllx %i2, 0x30, %o1
    0x001a3c7c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+88>: mov %i0, %o0
    0x001a3c80 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+92>: srax %o1, 0x30, %o1
    0x001a3c84 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+96>: call 0x182cb0 <__1cTGenReferenceManagerOGetCorrections6MrknKCLSGpsTime_rknICLSCoord_rnOCORRECTION_SET__nGRESULT__+3504>
    0x001a3c88 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+100>: add %fp, -1864, %o2
    0x001a3c8c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+104>: cmp %o0, 1
    0x001a3c90 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+108>: be,pn %icc, 0x1a3ca0 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+124>
    0x001a3c94 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+112>: mov %i0, %o0
    0x001a3c98 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+116>: ret
    0x001a3c9c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+120>: restore %g0, 0, %o0
    0x001a3ca0 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+124>: call 0x1a7068 <__1cSWPReferenceManagerPAdjustXTRATimes6MpnZCLSGnssSatellitePredictor_khrnKCLSGpsTime_rd_nGRESULT__+3584>
    0x001a3ca4 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+128>: add %fp, -1864, %o1
    0x001a3ca8 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+132>: ret
    End of assembler dump.
    =====================================
    (gdb) info registers
    g0 0x0 0
    g1 0xfd77ecb8 -42472264
    g2 0x11 17
    g3 0xecf0 60656
    g4 0xfd77e304 -42474748
    g5 0xfc 252
    g6 0x0 0
    g7 0xfeda4200 -19250688
    o0 0x1 1
    o1 0x20 32
    o2 0x693500 6894848
    o3 0xecf0 60656
    o4 0x6a21f0 6955504
    o5 0x1 1
    sp 0xfd77ec38 0xfd77ec38
    o7 0x1a3ca0 1719456
    l0 0x1b000021 452984865
    l1 0x2ca2a40 46803520
    l2 0x40173076 1075261558
    l3 0x57d22e16 1473392150
    l4 0x3fa80492 1067975826
    l5 0x3c06fe49 1007091273
    l6 0x4072b4a5 1081259173
    l7 0x410d711d 1091399965
    i0 0x421c0000 1109131264
    i1 0xffffffff -1
    i2 0x1d000018 486539288
    i3 0x2ca2808 46802952
    i4 0x40138e4a 1075023434
    i5 0x8b122e16 -1961742826
    fp 0xbfb17c3b 0xbfb17c3b
    i7 0xa817f0db -1474826021
    y 0x3 3
    psr 0xfe401007 -29356025
    wim 0x0 0
    tbr 0x0 0
    pc 0x1a3ca8 0x1a3ca8 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+132>
    npc 0x1a3cac 0x1a3cac <__1cSWPReferenceManagerOInputIonoModel6MrknKIONO_MODEL_khki_nGRESULT__>
    fsr 0x400420 4195360
    csr 0x0 0

  • Solaris 8 Installation - Exiting (caught signal 11)

    ----error message during installation----
    Starting Solaris Installation program
    Executing Jumpstart preinstall phase
    Searching for Solstart directory
    Checking rules.ok file
    Using begin script: install_begin
    Using finish script: patch_finish
    Executing Solstart preinstall phase�
    Executing begin script �install_begin��.
    Begin script install_begin execution completed.
    Exiting (caught signal 11)
    Type suninstall to restart
    After typing suninstall, it hang up and did not continue. I tried to re-install many times but same messages appeared. Please advise at the earliest.
    Machine Configuration I Used:
    Compaq Proliant 1600 Server
    Compaq 15" Monitor
    Video Driver = Cirrus Logic GD5446 (1MB)

    I don't have any removable media devices connected to this Compaq Proliant 1600 server. I even tried to disconnect the internal tape drive but the same messages I got.
    Please advise at the earliest.
    Thanks,
    Eder

  • Interrupting clnt_call in Solaris 10 using signals

    Is there a way to interrupt a clnt_call() before it times out in Solaris 10 using signals?
    Under Solaris 2.6, we were able to send a client a SIGINT, the client would accept the signal, reset the timeout using clnt_control() and then immediately time out of the clnt_call when the signal handler returned.
    Under Solaris 8, the SIGINT no longer interrupted the blocked clnt_call when the nsl library was dynamically linked in but we were able to statically link in libnsl.a from the 2.6 library and keep our interrupt functionality working.
    Under Solaris 10, this workaround no longer works. Signals, other than the ones with predefined actions like SIGKILL, SIGSTOP, etc., all get queued up until the clnt_call times out on its own. siginterrupt has no effect on the clnt_call blocking of signals.
    Thanks in advance for any information on this topic.

    The problem only occurs when we use INADDR_ANY to bind a socket. The program works as expected when we use real as well as virtual IP address configured for an interface on any Solaris Zone. When we use INADDR_ANY, error number is 14 (EFAULT, Bad Address).
    Just wondering if we need to make any configuration changes in order to allow INADDR_ANY to work.

  • SIGCHLD signal issue in Solaris 10

    I executing binaries on Solaris 10, but binaries are compiled on Solaris 8. Same binaries are working fine on Solaris 8 and Solaris 9 but not working on Solaris 10. Operating system is throughing SIGCHLD to my application. Also this is not consistant.
    Is there any change in Solaris 10 related to signals.

    I executing binaries on Solaris 10, but binaries are compiled on Solaris 8. Same binaries are working fine on Solaris 8 and Solaris 9 but not working on Solaris 10. Operating system is throughing SIGCHLD to my application. Also this is not consistant.
    Is there any change in Solaris 10 related to signals.

  • Solaris HotSpot Virtual Machine Error, Unexpected Signal 11 NEED HELP

    Hi all
    We are running a thin jsp application for video streaming live event running
    on a BEA WebLogic Personalization Server 3.2 on Solaris (streaming servers
    are separate and do not affect the server). After putting it in production
    we have experienced serious memory problems with our environment. When the
    servers are running under heavy load, they eat all available memory until
    they finally crash, please see log message below. We can see that the
    garbage collection is running but it doesn't seem to keep up with the memory
    consumption. The problem is described in a bug report at SUN, but it is
    marked as a "no fix" with the reasoning that programming resources are now
    allocated to jdk1.4?
    Log message:
    # HotSpot Virtual Machine Error, Unexpected Signal 11
    # Please report this error at
    # http://java.sun.com/cgi-bin/bugreport.cgi
    # Error happened during: scavenge
    # Error ID: 4F533F534F4C415249530E435050079A 01
    # Problematic Thread: prio=5 tid=0xdbea8 nid=0x4 runnable
    When this occured we ran JDK 1.3.0 with HotSpot Server VM on Solaris 8. WLS
    5.1, SP 9 and WLPS 3.2.
    WLS is started with the following parameters.
    #----------- Start WebLogic with the above parameters -----------
    $JDK_HOME/bin/java -server -ms512m -mx512m -Duser.timezone=ECT -classpath
    $JAVA_CLASSPATH -Dweblogic.system.bindAddr=10.122.114.4 -Dweblogic.cluster.m
    ulticastAddress=224.0.0.100 -Dweblogic.cluster.enable=true -Dweblogic.cluste
    r.name=iccluster -Dweblogic.class.path=$WEBLOGIC_CLASSPATH -Dweblogic.system
    .name=$SYSTEM_NAME
    weblogic.system.home=$SYSTEM_HOME -Dweblogic.home=$WEBLOGIC_HOME -Djava.secu
    rity.manager -Djava.security.policy=$WEBLOGIC_HOME/weblogic.policy -Dcommerc
    e.properties=$WL_COMMERCE_HOME/weblogiccommerce.properties -Dweblogic.proper
    ties=$WL_COMMERCE_HOME/weblogic.properties -Dpipeline.properties=$WL_COMMERC
    E_HOME/pipeline.properties -Dwebflow.properties=$WL_COMMERCE_HOME/webflow.pr
    operties -Dwlcs.home=$WL_COMMERCE_HOME weblogic.Server &
    We have now upgraded to jdk1.3.1_02 B02 but still have a problem with memory
    leaks. We have so far been able to restart the server before memory is
    exhausted and has hence not seen the same error message after the upgrade.
    The memory is not freed when Weblogic aborts, the SUN server has to be
    rebooted to free the memory. We now have to restart our 3 servers aprox.
    every 6 hours. The servers are equiped with 2G physical memory each. We have
    also tried setting hotspot to -client and setting -XX:MaxPerm.
    The HW configuration is as follows:
    1 Foundry Server Iron load balancer (with one hot stand by).
    3 Sun E420R, 2 x 440MHz CPU, 2GB RAM. Running in a cluster with one apache
    and one WLPS instance on each
    The SW configuration is as follows:
    JDK 1.3.1_02 B02 with HotSpot Server VM
    Solaris 8.
    WLS 5.1, SP 9
    WLPS 3.2.
    Oracle server 8.1.7
    Oracle client 8.1.6?
    This bug is described in
    http://developer.java.sun.com/developer/bugParade/bugs/4408730.html.
    It is also described as a known problem in
    http://www.weblogic.com/platforms/sun/index.html.
    It has also been described by SUN as a problem arising from multiple nested
    try/catch blocks appearing in generated java code from servlets, especially
    on WebLogic and Apache.
    As SUN has said that they will not fix this bug we are trying to find a
    workaround, but have yet found one. We have been looking into changing the
    heap size and setting GC options on the JVM, but haven't found the optimal
    solution. We would be very interested in experiences with tuning gc
    parameters, documentation on solaris patches for JVMs, JVM tuning, WebLogic
    tuning, HotSpot tuning.
    Has anyone experienced similar problems and found a workaround. We would be
    very happy to hear any suggestions as soon as possible,
    thanks
    Kris

    Perhaps the -noTryBlocks option to jspc might help you. See here:
    http://e-docs.bea.com/wls/docs61/////jsp/reference.html
    simon.

  • Signal catching in Solaris

    I tried to catch unique signal(SIGCHLD) from child processes.
    A problem is that parent should catch SIGCHLD signals from multiple children simultaneously.
    In Solaris 5.5 and 5.8, some of SIGCHLD signals disapear.
    But there is no zombie process.
    I think while a process catches one signal if the process gets same kind of signal, it blocks that signal in a queue.
    But in the real situation, kernel couldn't block same kind of signal.
    Plz, let me know why signals disapear.
    And how can I do catch all of them.
    FYI,
    I used sigaction function.
    Below, simple test program.
    #include <stdio.h>
    #include <sys/wait.h>
    #include <signal.h>
    #include <stdlib.h>
    #include <unistd.h>
    void child_do();
    void usr1_handle(int);
    void chld_handle(int);
    int main()
    int i;
    int pid;
    struct sigaction chld_act, usr1_act;
    printf("sigaction error\n");
    exit(1);
    for(i=0; i<5; i++)
    printf("%d : child create.\n",i+1);
    pid = fork();
    if (pid == 0)
    child_do();
    sleep(5);
    kill(0, SIGUSR1);
    while(1);
    return 0;
    void child_do()
    pause();
    void usr1_handle(int signo)
    if (getpid()==getpgrp())
    return;
    printf("receive SIGUSR1\n");
    exit(0);
    void chld_handle(int signo)
    int childPid, childStatus;
    childPid = wait(&childStatus);
    printf("%d : Child was killed!\n",childPid);

    Hope it gives you some clue:
    http://docs.sun.com/app/docs/doc/816-5137/6mba5vpju?a=view#gen-10856

  • SOLARIS SIGNALS in JAVA

    Hi,
    I am writing a java program which will be triggered by a shell script on solaris machine. how can i handle signals SIGUSR, SIGUSR2 etc... in the java program?
    Thanks in advance
    Regards
    Hunger

    Hi,
    the following trick might only work with some versions of Sun JDKs and is not recommended, however:
    There is a class called sun.misc.Signal and an interface sun.misc.SignalHandler which does, what you need. But use it with care! The VM uses its own signal handlers and might interfere with yours. There is an option to the VM "-Xrs" which influences how the VM handles signals and which signals it handles by itself.

  • JNI, Solaris and Signal 11

    There are a number of bugs in the database that have the following attributes:
    -JNI
    -Solaris
    -Signal 11 exceptions.
    -Long running applications.
    I am experiencing something similar. I was using C threads for some call back functionality (and of course registering it them with JNI.) I was hoping that starting the threads with java would help but it didn't.
    I have several questions:
    -Has anyone found anything that allows them to work around this? Doesn't matter what you think it was - like a different switch on an application server. I am just curious if anyone thinks they solved it in any way.
    -Does anyone have an idea what might cause it? Even an just an idle thought?
    -Does anyone have a long running application, that uses JNI on Solaris and they don't experience this (obviously the JVM itself does this, but I am still curious?)
    -And slightly different that the above, does anyone have a long running JNI Solaris application using C threads that doesn't have this problem?

    jschell, are you still experiencing this?
    You may have seen some of my posts before... I have seen many of yours. But I hadn't seen this one until now, by chance.
    I am running on Solaris 8 with Java 1.3.1_03 and have a multithreaded C/C++ program that invokes the JVM and makes calls into Java via JNI. Actually, I have a few programs like this, but a particular one is set up to run as a daemon and eventually (after a couple of hours) runs into a segmentation fault (signal 11). The stack in the core file when the program fails shows that a thread started in the native code attempted "AttachCurrentThread()" and then a segfault happens way down in the JVM somewhere. However, I had an issue like this previously and I tracked it down (unexpectedly) to a memory leak in a totally unrelated portion of the native code. So I am trying to find other memory leaks in the code using tools like Rational Purify but it is tricky to get Purify and the JVM to play nicely together.
    Additional info: I have all latest patches applied, not using signal handlers, and am using the "alternate" thread library in /usr/lib/lwp.
    - I have another similar program on Solaris that does not seem to have this problem.
    - The same program that's crashing on Solaris seems to run OK on both Windows and HP-UX.
    Given the above, I am pursuing the avenue of a memory corruption in the native code as that has turned out to be the cause of numerous other problems in the past, but I am having a very hard time with this one. jschell (or anyone else), please let me know about your status and what you think.
    Thanks -
    Chris

  • No signal at all after installing solaris-10 x86

    After successfully installing Solaris-10 x86 on my sytem when I try to boot , there is a Sendmail alert that "My unqualified host name sleeping for retry" and after that there is no signal on monitor . though CPU is running and accessing hard disk. This leave me with no option.
    System is not on the network and having Pentium-4 processor and 915G chipset motherbord.

    I'm guessing your X11 is misconfigured. You need to make the settings match what your monitor can display.

Maybe you are looking for