Application dumps core on solaris with BDB 4.6.21

Hi,
my application dumps core on solaris during the appication startup:
The solaris box detail is :
SunOS wcturgo3 5.10 Generic_137111-08 sun4v sparc SUNW,Netra-T5220.
I compiled the BDB with the following configuration:
./buildall.sh -p solaris -c cc -x CC -m gmake
the core file loks like :
fdc28c68 __db_pthread_mutex_init (50878, 0, 13, 0, ffbfca18, 0) + 88
fdca3bec __mutex_open (50878, 271638, 2058000, fdd47d1c, 271490, 0) + 224
fdce56ec __env_open (50878, 0, 880081, 8a0081, 0, 0) + 3bc
fdc206f4 int DbEnv::open(const char*,unsigned,int) (502f0, 0, 880081, 0, 502f0, fdce50c4) + 5c
fcb12824 void DbXml::Manager::initTempDbEnv(DbEnv*) (502d8, 503e0, 0, 15540, fe03c9f8, aa878) + 144
fcb11ea0 DbXml::Manager::Manager #Nvariant 1(unsigned) (502d8, 0, fe2ae760, 15540, fe03c9f8, 502d8) + 430
fcb059ec DbXml::XmlManager::XmlManager #Nvariant 1() (fe3697ec, fcdef0c0, fcdee994, 40, 13080, 0) + 24
fe234d68 NemiConfigToolInit::NemiConfigToolInit #Nvariant 1() (fe3697d4, 0, 0, 0, 0, fe36957c) + 60
fe2ae760 ???????? (0, 0, 0, 0, 0, 0)
fe2aeb04 ???????? (0, fc665440, aca5c, fe0272cc, fc665400, fe369544)
fe2f77d0 _init    (ff3f40fc, ff3f5a70, 2b3f4, 0, ff3f4910, 821) + f8
ff3c5280 call_init (60c10081, 1, ff2f0788, fe2f76d8, ff3f4910, ffdfffff) + 16c
ff3c47e8 setup (200000, 2801, 602, ff3f40fc, 60c10001, 446) + 1568
ff3d35cc _setup   (10034, ffffffff, 0, ff3b0000, ffffffff, ffffffff) + 40c
ff3b8480 rtboot (0, 0, 0, 0, 0, 0) + 88
00000000 ???????? (0, 0, 0, 0, 0, 0)
i tried using dbxml build with this BDB. i was able to execute one or two commands without the dbxml dumping core.
But my application dumps core during startup as sigbus (memory alignment issue).
I googled and found that people have faced problems of sigbus on solaris. when i checked with solaris, it seems that if the solaris box has 137111-0 to 137111-08 will face core dumps due to memory alignment issue which they say is because the application has misaligned mutex.
please suggest what should i do .
a)apply the sloaris kernel patch to temporary solution(as they claim the patch for thsi problem will give temporary solution .)
b) i have to compile the BDB with different options.

Hello,
You need to apply the patch below on top of Berkeley
DB 4.6.21:
*** dbinc/mutex_int.h     Tue Jul 01 15:03:43 2008 +1000
--- dbinc/mutex_int.h     Tue Jul 01 16:11:06 2008 +1000
*** 616,621 ****
--- 616,623 ----
#ifdef HAVE_MUTEX_SPARC_GCC_ASSEMBLY
typedef unsigned char tsl_t;
+
+ #define     MUTEX_ALIGN     8
#ifdef LOAD_ACTUAL_MUTEX_CODE
This corrects a Solaris-only alignment problem.
Thanks,
Sandra

Similar Messages

  • Application dumps core in 64-bit but runs fine in 32-bit

    Hi,
    I have a strange problem in a application supposed to be run in 64-bit mode. The application is a batch process run as a daemon. When it is compiled with 32-bit mode, it seems to be working fine, but when it is compiled with 64-bit mode, it dumps core after 30 min to 1 hr. This is not always predictable. The data where it dumps core is also not predictable. When I analysed the core, it shows the location, in a place where there seems to be no problem. I ran purify to check the memory leaks, and there is no memory leak in the code, except in the Forte STL (string).
    The core dump happens in a place where the message is read from a message queue and is assigned to a string. (i.e. assignment from char array to string). I have made sure that the pointers are not getting deleted twice.
    I am using the following environment
    SunOS archie 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-60
    Sun WorkShop 6 update 2 Compilers C++
    Sun WorkShop 6 update 2 Standard 64-bit Class Library for C++
    If anybody has any idea about the problem, please reply to this.
    Thanks a lot,
    H.M.Joisa

    Since the Configurator doesn't include a compiler, so the flash panel generated by it doesn't have a native height and width.
    So the height and width you assigned in the Configurator is saved into the .gpc file.
    You observation is very sharp and accurate, when a panel is opened first time in the Photoshop.
    It will show the panel in the default size first, then it will load the height and width you assigned from the .gpc file, and resize it to the size you want.
    And then when you close the panel, it will save the current panel size to a flash player share object.
    The next time when you open the panel, it will load the last time saved size back.

  • Studio 10 dbx dumps core with access checking on

    I have an application that causes Studio 10 dbx to dump core on start with access checking turned on. It will run OK under Studio 9 dbx, but tends to kill dbx if I attempt to follow the stack when a violation is found.
    For some odd reason, 'suppress rui' does not work with it as well.
    What information can I provide to help identify this bug? I expect the application and its build environment are too big to send in.
    Cheers,
    Ian

    x86/AMD64 doesn't do access checking, or does it now?
    Anyway, here is the pstack:
    Cheers, Ian.
    core '/tmp/core' of 12721: /opt/studio10/SUNWspro/bin/../prod/bin/sparcv9/dbx sm70/icp/test/sparc
    ffffffff7e6a39c0 _kill (ffffffff7e7b0f88, 31b1, 2002, 100532d9d, 100532000, 100532) + 8
    00000001000bbaa4 ???????? (10062e, 100400, b, 100400, 100633000, 10053f5e0)
    ffffffff7e6a2dfc sigacthandler (b, ffffffff7fff8850, ffffffff7fff8570, b, 3d, 3d000000) + 2c
    --- called from signal handler with signal 11 (SIGSEGV) ---
    000000010025881c __1cHTypetabHGetType6Mii_pnEType__ (ffffffff7fffe738, 100999670, 100999680, 0, 0, ffffffff7
    fffb892) + c
    000000010029a01c __1cFStabsQmake_tactarglist6MpcrnHSymlist_pnHObjfile_ibb_2_ (ffffffff7fffe738, 7c, 1, 10099
    9670, 0, 0) + 104
    000000010029ae90 __1cFStabsZcafe_parse_templ_fun_inst6MpnHObjfile_pnDFun_pc5b_4_ (ffffffff7fffe738, 10099967
    0, 1009ba7d0, 1, ffffffff7d340fc2, ffffffff7fffb884) + 24c
    0000000100286c60 __1cFStabsIFuncDecl6MpnHObjfile_pnDFun_pcb_4_ (ffffffff7fffe738, 100999670, 1009ba990, 5f,
    4c, 1009ba990) + ec
    0000000100282828 __1cFStabsSNPatchProcessDebug6MpnHObjfile_pnEstab_pcIIbb_I_ (ffffffff7fffe738, 100999670, f
    fffffff7d349e14, ffffffff7d31df38, ffffffff7d34f364, ffffffff7fffe66c) + 1d8
    000000010024b478 ???????? (10076b050, 49e14, 0, de6, 0, 1)
    000000010024b8d8 ???????? (100999670, ffffffffffffffff, 103955440, 102eb6730, 1, 1)
    000000010024b6a8 __1cNReadLazyStabs6FpnHObjfile_bb_v_ (100999670, 10053f000, 1, 1, 10053f5e0, 100400) + e4
    00000001001dbae8 __1cGRtcFunTlocate_npatch_sites6M_v_ (103933330, 7, e, 80, 84, 103933330) + 80
    00000001001db888 __1cGRtcFunSlocate_patch_sites6ML_i_ (103933330, 51eb8400, ed11ad88, 100999a60, 81c7e008, 1
    ) + 784
    00000001001d6544 __1cKRtcLoadObjRrtc_process_check6Mb_v_ (103933330, 100400, 100983860, 1009c4e70, 100983870
    , ffffffffffffffff) + 6fc
    00000001001c714c __1cGRtcMgrPrtc_new_process6M_v_ (102c1ae30, 10065a400, 0, 0, 1, 10056fe74) + 80c
    00000001001c590c __1cGRtcMgrTtry_rtc_new_process6M_b_ (10065a400, 1005d4d05, 0, 10056f000, 10056f, 10076ac30
    ) + c
    00000001001c5544 ???????? (1, 1029df5a9, 10053f5e0, 10065a400, 5, 1002452c8)
    00000001000c7984 __1cSActionList_execute6FpnEList4nGAction___pnEProc_pnHHandler_pnJEventInst_nHLevel_e__v_ (
    102d13780, 102cb0340, 102d1e1c0, 102ab71d0, 1, 10053b) + 64
    0000000100166a4c __1cHHandlerSdecision_procedure6MpnEProc__v_ (102d1e1c0, 102cb0340, 100558, 100400, 1005585
    bc, 102ab71d0) + 158
    00000001001bfccc __1cKRecognizerHtrigger6MpnEProc__v_ (102d1e1c0, 102cb0340, 100400, 100581000, 100581ea8, 1
    0056c18d) + e8
    00000001001c0240 __1cKRecognizerIdispatch6FpnGTarget_pnEProc__v_ (10053f5e0, 102cb0340, 100400, 1, 0, 10064e
    370) + 58
    00000001001b0c44 __1cEProcNvcpu_dispatch6MpnEVCpu__b_ (102cb0340, 100766070, 1005468d0, 1002182a0, 100769888
    , 100645d30) + 384
    00000001001b0de8 __1cEProcQpervcpu_dispatch6MpnEVCpu__v_ (102cb0340, 10057c3d0, 102d3bc60, 10057c450, 10057c
    3d0, 100569599) + 14c
    00000001001b15d4 __1cEProcQgeneric_dispatch6MpnEVCpu__b_ (102cb0340, 10057c458, 100569, 100581000, 10056972b
    , 100581) + 1a8
    00000001001b1d4c __1cEProcCgo6MpnEVCpu_nGProcGo_b_v_ (102cb0340, 100569, 102be9050, cc4, 100581fe8, 1) + 52c
    000000010017ca14 __1cGdo_run6FpnGInterp_bnHLevel_e__i_ (100400, 100568000, 100400, 10053f5e0, 100400, 100400
    ) + 328
    00000001002bbba0 ???????? (1005983f7, 102ab8230, 10065b8d8, 0, 10066f510, 102b487e0)
    00000001002ba890 __1cNpdksh_execute6FpnGInterp_pnCop_i_i_ (10065b890, 102c81dc0, 0, 10065b890, 102bcf5a0, 10
    3539140) + 1c0
    00000001002a710c __1cLpdksh_shell6FpnGInterp_pnGSource__i_ (10065b890, 102cf6280, 100400, 100596d79, 100596d
    80, 1000bb4b0) + 4c0
    00000001000bfa5c __1cNmain_cmd_loop6FpnGInterp__v_ (10065b890, 100400, 100533d18, 100614178, 100581f10, 1005
    33) + a8
    00000001000c0a8c main (100400, 100532, 100533d18, 10065b890, 10053f5e0, 1) + b8c
    00000001000b409c _start (0, 0, 0, 0, 0, 0) + 17c                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Core dump/hang problem solaris 8

    Hello ,
    I am using the following configuration, to build my application
    SunOS 5.8 Generic_108528-12 sun4u sparc
    SUNW,Ultra-5_10
    64 bit machine with CC 5.0
    While excuting the program i get core dump/hang in cout , following is the stack looking from dbx
    [1] mutexadaptive_lock(0xffffffff7c322000, 0xffffffff7c331670, 0x4c00, 0x1000, 0xfffeffff, 0x1), at 0xffffffff7c20daac
    [2] cmutexlock(0x10017eca0, 0x20, 0x20, 0x10002f66c, 0x0, 0x0), at 0xffffffff7c20d870
    [3] std::locale::__install(0x10, 0x10017ec90, 0x0, 0xffffffff7fffe7e0, 0x0, 0x0), at 0x10002f66c
    [4] std::locale::__make_explicit(0x100047a90, 0x0, 0x0, 0x10017ec90, 0x100176570, 0x100170068), at 0x10002f514
    [5] std::basic_filebuf<char,std::char_traits<char> >::overflow(0x10016f620, 0x73, 0x10016f620, 0x0, 0x0, 0x0), at 0x10004759c
    [6] std::basic_filebuf<char,std::char_traits<char> >::sync(0x10016f620, 0x10016f620, 0x0, 0x0, 0x0, 0x0), at 0x1000497c8
    [7] std::basic_ostream<char,std::char_traits<char> >::sentry::~sentry(0xffffffff7fffeb30, 0xffffffff7fffec50, 0x73, 0x73, 0x73, 0x0), at 0x10002c0bc
    [8] std::operator<<(0x10016f7f0, 0x10016f800, 0x10016f7f0, 0x73, 0x0, 0x100063cf0), at 0x10002b70c
    [9] usage(0x10016f900, 0x1001706d8, 0x1001706c0, 0x10016f930, 0x10016f910, 0x10016f888), at 0x10001d1cc
    [10] main(0x1, 0xffffffff7ffff5d8, 0xffffffff7ffff5e8, 0x0, 0x0, 0x100000000), at 0x10001ad34
    Any ideas regarding this,
    Thanks and Regards
    Amol

    Hi,
    I didnt compile with -g option, but i got to the root of problem. In the program I was just doing cout , so it was very simple, but I was linking libpthread library with the program , also was giving -mt flag during compilation. When I removed this both, the program disn't dump core and nither did it hang.
    But the same thing worked with solaris 2.8 64 bit CC 5.0 with patch 108528-10 .
    So I just can make out the difference as to why this this is happening
    Regards
    Amol

  • BDB dumps core after adding approx 19MB of data

    Hi,
    BDB core dumps after adding about 19MB of data & killing and restarting it several times.
    Stack trace :
    #0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
    (gdb) bt
    #0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
    #1 0xc000000000260cf0:0 in raise+0x30 () from /usr/lib/hpux64/libc.so.1
    #2 0xc0000000002fe710:0 in abort+0x190 () from /usr/lib/hpux64/libc.so.1
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_err.o.
    If NOT specified will behave as a non -g compiled binary.
    warning: No unwind information found.
    Skipping this library /integhome/jobin/B063_runEnv/add-ons/lib/libicudata.sl.34.
    #3 0xc000000022ec2340:0 in __db_assert+0xc0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_meta.o.
    If NOT specified will behave as a non -g compiled binary.
    #4 0xc000000022ed2870:0 in __db_new+0x780 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile bt_split.o.
    If NOT specified will behave as a non -g compiled binary.
    #5 0xc000000022ded690:0 in __bam_root+0xb0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    #6 0xc000000022ded2d0:0 in __bam_split+0x1e0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile bt_cursor.o.
    If NOT specified will behave as a non -g compiled binary.
    #7 0xc000000022dc83f0:0 in __bam_c_put+0x360 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_cam.o.
    If NOT specified will behave as a non -g compiled binary.
    #8 0xc000000022eb8c10:0 in __db_c_put+0x740 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_am.o.
    If NOT specified will behave as a non -g compiled binary.
    #9 0xc000000022ea4100:0 in __db_put+0x4c0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so---Type <return> to continue, or q <return> to quit---
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_iface.o.
    If NOT specified will behave as a non -g compiled binary.
    #10 0xc000000022eca7a0:0 in __db_put_pp+0x240 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile cxx_db.o.
    If NOT specified will behave as a non -g compiled binary.
    #11 0xc000000022d92c90:0 in Db::put(DbTxn*,Dbt*,Dbt*,unsigned int)+0x120 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    What is the behaviour of BDB if its killed & restarted when a bdb transaction is in progress?
    anybody has an idea as to why BDB dumps core in above scenario?
    Regards
    Sandhya

    Hi Bogdan,
    As suggested by you i am using the below flags to open an enviornment.
    DB_RECOVER |DB_CREATE | DB_INIT_LOG | DB_INIT_MPOOL | DB_INIT_TXN|DB_THREAD
    DB_INIT_LOCK is not used because at our application level we are maintaining a lock to guard against multiple simultaneous access.
    The foll msg is output on the console & the dumps core with same stack trace as posted before.
    __db_assert: "last == pgno" failed: file "../dist/../db/db_meta.c", line 163
    I ran db_verify, db_stat, db_recover tools on the DB & thier results are as below.
    db_verify <dbfile>
    db_verify: Page 4965: partially zeroed page
    db_verify: ./configserviceDB: DB_VERIFY_BAD: Database verification failed
    db_recover -v
    Finding last valid log LSN: file: 1 offset 42872
    Recovery starting from [1][42200]
    Recovery complete at Sat Jul 28 17:40:36 2007
    Maximum transaction ID 8000000b Recovery checkpoint [1][42964]
    db_stat -d <dbfile>
    53162 Btree magic number
    9 Btree version number
    Big-endian Byte order
    Flags
    2 Minimum keys per-page
    8192 Underlying database page size
    1 Number of levels in the tree
    60 Number of unique keys in the tree
    60 Number of data items in the tree
    0 Number of tree internal pages
    0 Number of bytes free in tree internal pages (0% ff)
    1 Number of tree leaf pages
    62 Number of bytes free in tree leaf pages (99% ff)
    0 Number of tree duplicate pages
    0 Number of bytes free in tree duplicate pages (0% ff)
    0 Number of tree overflow pages
    0 Number of bytes free in tree overflow pages (0% ff)
    0 Number of empty pages
    0 Number of pages on the free list
    db_stat -E <dbfile>
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Default database environment information:
    4.3.28 Environment version
    0x120897 Magic number
    0 Panic value
    2 References
    0 The number of region locks that required waiting (0%)
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Per region database environment information:
    Mpool Region:
    2 Region ID
    -1 Segment ID
    1MB 264KB Size
    0 The number of region locks that required waiting (0%)
    Log Region:
    3 Region ID
    -1 Segment ID
    1MB 64KB Size
    0 The number of region locks that required waiting (0%)
    Transaction Region:
    4 Region ID
    -1 Segment ID
    16KB Size
    0 The number of region locks that required waiting (0%)
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_ENV handle information:
    Set Errfile
    db_stat Errpfx
    !Set Errcall
    !Set Feedback
    !Set Panic
    !Set Malloc
    !Set Realloc
    !Set Free
    Verbose flags
    !Set App private
    !Set App dispatch
    !Set Home
    !Set Log dir
    /integhome/jobin/B064_July2/runEnv/temp Tmp dir
    !Set Data dir
    0660 Mode
    DB_INIT_LOG, DB_INIT_MPOOL, DB_INIT_TXN, DB_USE_ENVIRON Open flags
    !Set Lockfhp
    Set Rec tab
    187 Rec tab slots
    !Set RPC client
    0 RPC client ID
    0 DB ref count
    -1 Shared mem key
    400 test-and-set spin configuration
    !Set DB handle mutex
    !Set api1 internal
    !Set api2 internal
    !Set password
    !Set crypto handle
    !Set MT mutex
    DB_ENV_LOG_AUTOREMOVE, DB_ENV_OPEN_CALLED Flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Default logging region information:
    0x40988 Log magic number
    10 Log version number
    1MB Log record cache size
    0660 Log file mode
    1Mb Current log file size
    632B Log bytes written
    632B Log bytes written since last checkpoint
    1 Total log file writes
    0 Total log file write due to overflow
    1 Total log file flushes
    1 Current log file number
    42872 Current log file offset
    1 On-disk log file number
    42872 On-disk log file offset
    1 Maximum commits in a log flush
    1 Minimum commits in a log flush
    1MB 64KB Log region size
    0 The number of region locks that required waiting (0%)
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Log REGINFO information:
    Log Region type
    3 Region ID
    __db.003 Region name
    0xc00000000b774000 Original region address
    0xc00000000b774000 Region address
    0xc00000000b883dd0 Region primary address
    0 Region maximum allocation
    0 Region allocated
    REGION_JOIN_OK Region flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_LOG handle information:
    !Set DB_LOG handle mutex
    0 Log file name
    !Set Log file handle
    Flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    LOG handle information:
    0 file name list mutex (0%)
    0x40988 persist.magic
    10 persist.version
    0 persist.log_size
    0660 persist.mode
    1/42872 current file offset LSN
    1/42872 first buffer byte LSN
    0 current buffer offset
    42872 current file write offset
    68 length of last record
    0 log flush in progress
    0 Log flush mutex (0%)
    1/42872 last sync LSN
    1/41475 cached checkpoint LSN
    1MB log buffer size
    1MB log file size
    1MB next log file size
    0 transactions waiting to commit
    1/0 LSN of first commit
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    LOG FNAME list:
    0 File name mutex (0%)
    1 Fid max
    ID Name Type Pgno Txnid DBP-info
    0 configserviceDB btree 0 0 No DBP 0 0 0
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Default cache region information:
    1MB 262KB 960B Total cache size
    1 Number of caches
    1MB 264KB Pool individual cache size
    0 Maximum memory-mapped file size
    0 Maximum open file descriptors
    0 Maximum sequential buffer writes
    0 Sleep after writing maximum sequential buffers
    0 Requested pages mapped into the process' address space
    43312 Requested pages found in the cache (89%)
    4968 Requested pages not found in the cache
    640 Pages created in the cache
    4965 Pages read into the cache
    621 Pages written from the cache to the backing file
    4818 Clean pages forced from the cache
    621 Dirty pages forced from the cache
    0 Dirty pages written by trickle-sync thread
    166 Current total page count
    146 Current clean page count
    20 Current dirty page count
    131 Number of hash buckets used for page location
    53888 Total number of times hash chains searched for a page
    4 The longest hash chain searched for a page
    92783 Total number of hash buckets examined for page location
    0 The number of hash bucket locks that required waiting (0%)
    0 The maximum number of times any hash bucket lock was waited for
    0 The number of region locks that required waiting (0%)
    5615 The number of page allocations
    10931 The number of hash buckets examined during allocations
    22 The maximum number of hash buckets examined for an allocation
    5439 The number of pages examined during allocations
    11 The max number of pages examined for an allocation
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Pool File: temporary
    1024 Page size
    0 Requested pages mapped into the process' address space
    43245 Requested pages found in the cache (99%)
    1 Requested pages not found in the cache
    635 Pages created in the cache
    0 Pages read into the cache
    617 Pages written from the cache to the backing file
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Pool File: configserviceDB
    8192 Page size
    0 Requested pages mapped into the process' address space
    65 Requested pages found in the cache (1%)
    4965 Requested pages not found in the cache
    1 Pages created in the cache
    4965 Pages read into the cache
    0 Pages written from the cache to the backing file
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Mpool REGINFO information:
    Mpool Region type
    2 Region ID
    __db.002 Region name
    0xc00000000b632000 Original region address
    0xc00000000b632000 Region address
    0xc00000000b773f08 Region primary address
    0 Region maximum allocation
    0 Region allocated
    REGION_JOIN_OK Region flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    MPOOL structure:
    0/0 Maximum checkpoint LSN
    131 Hash table entries
    64 Hash table last-checked
    48905 Hash table LRU count
    48914 Put counter
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_MPOOL handle information:
    !Set DB_MPOOL handle mutex
    1 Underlying cache regions
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_MPOOLFILE structures:
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    MPOOLFILE structures:
    File #1: temporary
    0 Mutex (0%)
    0 Reference count
    18 Block count
    634 Last page number
    0 Original last page number
    0 Maximum page number
    0 Type
    0 Priority
    0 Page's LSN offset
    32 Page's clear length
    0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 f8 0 0 0 0 ID
    deadfile, file written Flags
    File #2: configserviceDB
    0 Mutex (0%)
    1 Reference count
    148 Block count
    4965 Last page number
    4964 Original last page number
    0 Maximum page number
    0 Type
    0 Priority
    0 Page's LSN offset
    32 Page's clear length
    0 0 b6 59 40 1 0 2 39 ac 13 6f 0 a df 18 0 0 0 0 ID
    file written Flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Cache #1:
    BH hash table (131 hash slots)
    bucket #: priority, mutex
    pageno, file, ref, LSN, mutex, address, priority, flags
    bucket 0: 47385, 0/0%:
    4813, #2, 0, 0/1, 0/0%, 0x04acf0, 47385
    4944, #2, 0, 0/0, 0/0%, 0x020c18, 48692

  • Core Dump on x86 Solaris 8

    Sorry for posting on Linux thread. I could not find area related to this problem.
    I have x86 box (256MB 10GB) running Solaris 8 and Oracle Enterprise 8.15. I have it all configured and running. Howerver, when I startup the database and the tns listner I get core dump every 4-5 hours and the box reboots. After examining the crash message I found out it was GPF. I am sure that Oracle is the cause of the problem, because I stoped the database and listener and machine does not crash anymore. I still have the core file if anyone in Oracle is interested

    Hi,
    I didnt compile with -g option, but i got to the root of problem. In the program I was just doing cout , so it was very simple, but I was linking libpthread library with the program , also was giving -mt flag during compilation. When I removed this both, the program disn't dump core and nither did it hang.
    But the same thing worked with solaris 2.8 64 bit CC 5.0 with patch 108528-10 .
    So I just can make out the difference as to why this this is happening
    Regards
    Amol

  • SAP CRM middleware problem (sysfail ) The current application has triggered a termination with short dump

    i'm having a proplem during  starting initial load although i'm using the best practice documents C71 and B09 and all the configration was done by them .... could any one help ??

    this is the first dump error for my RFCUSER on the ECC server
    Category               ABAP Programming Error
    Runtime Errors         MESSAGE_TYPE_X
    ABAP Program           SAPLCRMC
    Application Component  CA
    Date and Time          05.03.2014 17:50:47
    Short Text
         The current application has triggered a termination with a short dump.
    What happened?
         The current application program has detected a situation that should
         not occur. A termination with short dump has therefore been triggered
         by the key word MESSAGE (type X).
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
    Error analysis
        Short text of the error message:
        See SAP Note 1498111
        Long text of the error message:
         Diagnosis
         System Response
         Procedure
             Refer to the SAP Note that was mentioned.
         Procedure for System Administration
        Technical information about the message:
        Message class....... C_
        Number.............. 330
        Variable 1.......... 1498111
        Variable 2..........
        Variable 3..........
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        If the error occurs in a non-modfied SAP program, you might be able to
        find a solution in the SAP Notes system. If you have access to the SAP
        Notes system, check there first using the following keywords:
        "MESSAGE_TYPE_X"
        "SAPLCRMC" bzw. LCRMCF0C
        "CHECK_CRMATAB"
        If you cannot solve the problem yourself, please send the following
        information to SAP:
        1. This description of the problem (short dump)
        To do this, choose  System -> List -> Save -> Local File (unconverted)
        on the screen you are in now.
        2. A suitable system log
        To do this, call the system log in transaction SM21. Restrict the time
        interval to ten minutes before the short dump and five minutes after
        it. In the display, choose System -> List -> Save -> Local File
        (unconverted).
    3. If these are programs of your own, or modified SAP programs: Source
    code of these programs
    To do this, choose  More Utilities -> Upload/Download -> Download in
    the Editor.
    4. Details regarding the conditions under which the error occurred or
    which actions and input caused the error.
    thanks

  • What application does an iMac come with that lets you see the core of its system, and what would you look for to determine if malware was on it?

    What application does an iMac come with that lets you see the core of its system, and what would you look for to determine if malware was on it?

    This extension?
    *FireBug: https://addons.mozilla.org/firefox/addon/firebug/
    Firefox 4 also has a build in inspector: Firefox > Web Developer > Inspect

  • Process dumps core, when started by SMF - fine when manually started

    Hi.
    h2. Explanation
    I compiled [Nagios 3.2.0|http://www.nagios.org/] manually, and created a SMF manifest and method file, based on the [OpenCSW supplied files for Nagios|http://www.opencsw.org/packages/nagios]. The method file is based on [what the Nagios guys supply|http://pastebin.ca/1577792] , but [changed a little|http://pastebin.ca/diff.php?id1=1577792&id2=1577793] .
    When I enable the "application/nagios" service, it right away goes into maintenance state. In the /var/svc/log/application-nagios:default.log log file, there's consequently then this:
    + exit 0
    [ Sep 24 13:17:10 Method "start" exited with status 0 ]
    [ Sep 24 13:17:11 Stopping because process dumped core. ]
    [ Sep 24 13:17:11 Executing stop method ("/opt/local/nagios-3.2.0/method/nagios stop") ]
    + test -r /lib/svc/share/smf_include.sh
    [...]It died, because of "*Stopping because process dumped core.*"
    If you have a look at the method file, you'll find that I dump the environment with env to a file. When I login as root and set the environment variables to exactly those values and remove any other additional variables, I can run the method / init script just fine; the nagios process doesn't core dump.
    h2. Question
    Why does the process dump core, when it's run by SMF?
    Additional questoin:Where's the core dump? I did a "find / -name core" and found nothing. I also changed coreadm:
    --($ ~)-- LC_ALL=C coreadm
         global core file pattern: /var/core/core.%f.%pAfter a reboot, there's nothing in /var/core (the directory exists).
    I'm on Solaris 10 5/09 Sparc.
    h2. Files
    *[svccfg export nagios|http://pastebin.ca/1577787]*
    *[Method file /opt/local/nagios-3.2.0/method/nagios|http://pastebin.ca/1577793]*

    There's no such directory as "/var/crash":
    --($ ~)-- ls -lad /var/c*
    drwxr-xr-x    4 root     sys             4 Sep 21 14:03 /var/cache
    drwxr-xr-x    2 root     sys             7 Sep 21 13:32 /var/cc-ccr
    drwxr-xr-x    2 root     root            2 Sep 24 13:14 /var/core
    drwxr-xr-x    2 root     sys             3 Sep 21 14:03 /var/cronGranted, since when I posted that question and now, I booted the NGZ numerous times. But in a default installation of Solaris 10, that directory isn't removed during shutdown/boot, if it exist. At least it exists on my other servers, even if it is empty (eg. like that, on a different server:
    --($ ~)-- ls -laR /var/crash/
    /var/crash/:
    total 3
    drwxr-xr-x    3 root     root          512 Mai 19  2006 .
    drwxr-xr-x   56 root     sys          1024 Dez  7  2008 ..
    drwxrwx---    2 root     adm           512 Sep 22  2008 winds06
    /var/crash/winds06:
    total 2
    drwxrwx---    2 root     adm           512 Sep 22  2008 .
    drwxr-xr-x    3 root     root          512 Mai 19  2006 ..So, I'd say that the coredump has never been stored in /var/crash.
    Anyway - isn't /var/crash just used for crashdumps, when the whole machine goes down? According to [man filesystem(5)|http://docs.sun.com/app/docs/doc/816-5175/filesystem-5?a=view] , it is &#8594; "+Default depository for kernel crash dumps.+"
    If coredumps aren't in /var/crash, aren't named "core*" and aren't stored in the directory specified by coreadm, where are they?
    Converse: If no coredump is created, why does Solaris "speak" about a coredump being created?

  • Mdb dumps core (duh)

    While attempting to resolve a problem with mod_ssl vs. Sun Apache-1.3.27 (SUNWapch{d,r,u} with patch 113246-02), I decided to run apache trough mdb.
    # mdb /usr/apache/bin/httpd
    Loading modules: [ libc.so.1 ]
    :cmdb: fork1 detected: follow (p)arent or (c)hild? c
    mdb: target forked child process 135 (debugger following child)
    Segmentation Fault (core dumped)
    # file core
    core: ELF 32-bit MSB core file SPARC Version 1, from 'mdb'
    # pstack core
    core 'core' of 219: mdb /usr/apache/bin/httpd
    ff30d028 ps_ptread (0, ff3f8000, ffbfe4fc, 2c, 0, 0) + 4
    ff2e15e4 rdevent_getmsg32 (bc1f0, ffbfe5e8, 0, 0, 0, 0) + 24
    ff2e0ba8 rd_event_getmsg (bc1f0, ffbfe5e8, 0, 0, 20, 0) + 14
    0003ce8c pt_rtld_event (a7ad8, fffffff8, 0, 1, 4ca68, 77400) + 14
    00048c88 tgt_continue (77688, ffbfeb44, 7b9f8, 0, 0, 4014bc) + 520
    00048e10 tgt_request_continue (a7ad8, ffbfeb44, 100, 41b04, 0, 0) + 1c
    00024aa4 cmd_cont_common (0, 0, 0, 0, 48fb4, 56930) + 158
    0001f5a8 dcmd_invoke (7c498, 0, 0, 0, 0, 0) + 4c
    0001f78c mdb_call_idcmd (0, 0, 0, 1, 0, 0) + 114
    0001f0ec mdb_call (0, 0, 0, 1, 0, 83850) + 33c
    0004edc0 yyparse (53acc, 77000, 53504, 52d2c, ff676980, 130) + 63c
    0001eb5c mdb_run (0, 34c7c, 0, ffbffee2, 2f757372, 2d000000) + 274
    00035e4c main (0, 0, 77564, 43c00, 34000, 44c00) + 1078
    000189e0 _start   (0, 0, 0, 0, 0, 0) + 108
    Now if my own programs happen to dump core, that's my problem. But if the debugger itself crashes, things start to look a bit bleak indeed.
    The system in question is a SunBlade 2000, Solaris 9 with yesterday's recommended patches applied.
    Any hints?
    Regards, Paul Boven.
    P.S. although this is not a C-compiler issue in itself, I felt that this developer forum was the most appropriate place to post this.

    mdb(1) is an OS command supported with adb for
    debugging calls into the kernel. For better results,
    I recommend that this question be posted to one of
    the Solaris discussion groups. This product is not
    maintained under the Compiler Collection or Sun One
    Studio.

  • Segmentation Fault in db- put() fun with BDB ver 4.5.20/4.6.19 in linux

    I am working on porting an application that runs on sun solaris sparc (OS ver 5.8) with Berkeley DB ver 4.2.50 into suse linux [ Linux version 2.6.5-7.244-smp (gcc version 3.3.3 (SuSE Linux)) ]. I have compiled the application in linux and i am getting segmentation fault error while running the application. The error occurs while the objects are loaded from the database into berkeley cache. The application fails in db->put function while loading the objects. This segmentation fault error is not consistently occuring every time on the same object. Sometimes it throws the error while loading the first object itself or sometimes it throws after loading couple of objects. But the stack trace shows the same function whenever it crashes.
    Given below is the stack trace of the application when it throws SIGSEGV.
    [INFO] [-1756589376] 14:23:24.406 BerkeleyCache : restoring database table metadata for table [BSCOffice]...
    [INFO] [-1756589376] 14:23:24.406 BerkeleyCache : restoring database index metadata for table [BSCOffice]...
    [INFO] [-1756589376] 14:23:24.408 Obj [BSCOffice] Col [BSCOfficeId] : Typ[TEXT] MaxLen[10] Null[Y]
    [INFO] [-1756589376] 14:23:24.408 Obj [BSCOffice] Col [City] : Typ[TEXT] MaxLen[100] Null[Y]
    [INFO] [-1756589376] 14:23:24.408 BerkeleyCache : creating table [BSCOffice.tbl]
    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 182927004352 (LWP 14638)]
    0x0000002a9643203a in __db_check_txn () from /opt/home/pesprm/local/db-4.6.19/db-4.6.19/build_unix/.libs/libdb-4.6.so
    (gdb) where
    #0 0x0000002a9643203a in __db_check_txn () from /opt/home/pesprm/local/db-4.6.19/db-4.6.19/build_unix/.libs/libdb-4.6.so
    #1 0x0000002a9643475b in __db_put_pp () from /opt/home/pesprm/local/db-4.6.19/db-4.6.19/build_unix/.libs/libdb-4.6.so
    #2 0x000000000043586b in esp::BerkeleyCache::insert_i (this=0x7fbfffe380, transactionId=866640768, pObj=0x7fbfffd3e0) at BerkeleyCache.cpp:838
    #3 0x00000000004119c5 in RefServer::loadObject (this=0x7fbfffdbe0, objInfo=<value optimized out>, strPrimaryObjName=@0x7fbfffd6f0,
    procParams=<value optimized out>) at BerkeleyCache.h:569
    #4 0x0000000000419166 in RefServer::loadObjects (this=0x7fbfffdbe0) at RefServer.cpp:579
    #5 0x0000000000419748 in main (argc=<value optimized out>, argv=<value optimized out>) at RefServer.cpp:296
    The code that calls the db->put() function is given below:
    <pre>
    bool BerkeleyCache::insert_i(size_t transactionId, const CachePersistable* pObj)
         bdbcache::Table* pTable = findTable_i(pObj->getPersistInfo().getObjectName());
         if (pTable == NULL)
              return false;
         DB_TXN* txnp = (DB_TXN*)transactionId;
         if (txnp == NULL)
              return false;
         bdbcache::Index* pPrimaryKey = pTable->getPrimaryKey();
         if (pPrimaryKey == NULL)
              return false;
         if (pTable->getDataOffset() == -1)
              pTable->setDataOffset( (int)(pObj->getDataBufferStartPos() - pObj->getDataStartPos()) );
         DB* pdb = pTable->getDB();
         int rc = 0;
         Synchronize sync(pPrimaryKey->getKeyBufferCriticalSection());
         pPrimaryKey->getKeyValues(pObj, pPrimaryKey->getKeyBuffer());
         DBT key, data;
         memset(&key, 0, sizeof(DBT));
         key.flags = DB_DBT_USERMEM;
         key.data = (void*)pPrimaryKey->getKeyBuffer().getBuffer();
         key.ulen = key.size = pPrimaryKey->getKeyBuffer().getBufferLength();
         memset(&data, 0, sizeof(DBT));
         data.flags = DB_DBT_USERMEM;
         if (pTable->isPrimaryDb())
              data.data = (void*)pObj->getDataBufferStartPos();
              data.ulen = data.size = pObj->getDataBufferSize();
              rc = pdb->put(pdb, (DB_TXN*)transactionId, &key, &data, DB_NOOVERWRITE);
         else
              const PersistInfo::Property* prop = pTable->getJoinProperty();
              Variant var = pObj->getValue( prop );
              int n = 0;
              switch (prop->_eType)
                   case PersistInfo::CHAR_ARRAY:
                   case PersistInfo::STRING:
                   case PersistInfo::VAR_STRING:
                        const char* pch = (const char*)var;
                        data.data = (void*)pch;
                        data.ulen = data.size = (int)strlen(pch) + 1;
                        break;
                   case PersistInfo::INT:
                        n = (int)var;
                        data.data = (void*)&n;
                        data.ulen = data.size = sizeof(int);
                        break;
              rc = pdb->put(pdb, (DB_TXN*)transactionId, &key, &data, 0);
         if (rc!= DB_SUCCESS)
              //_app.logError("BerkeleyCache : DB->put() failed [%s]", db_strerror(rc));
              _app.logInfo("ERROR:BerkeleyCache : DB->put() failed [%s]", db_strerror(rc));
              return false;
         return true;
    </pre>
    At the end of this function, the return value of db->put is checked for DB_SUCCESS. The application never executed this line when it throws SIGSEGV.
    I have tried using the BDB versions 4.5.20/4.6.18/4.6.19 with the application and it throws segmentation fault error with all versions of BDB. Following are the cache related configurable parameters that we use in our application.
    cache size = 16 MB
    page size = 16 KB
    max locks = 3000000
    dirty read = N
    We are using the Sybase Adaptive DB server running in Solaris/Linux servers. The same application that runs in Solaris connecting to Sybase DB (in solaris) is working perfectly fine. And the application that i am working in linux connects to the Sybase DB running in linux server.
    Please let me know what could be the issue that is causing our application to segmentation fault.
    Thanks
    Senthil

    I am working on porting an application that runs on
    sun solaris sparc (OS ver 5.8) with Berkeley DB ver
    4.2.50 into suse linux [ Linux version
    2.6.5-7.244-smp (gcc version 3.3.3 (SuSE Linux)) ].
    I have compiled the application in linux and i am
    getting segmentation fault error while running the
    application. The error occurs while the objects areWhich indicates in almost every typical case, for a well used library like berkeleydb, an application issue.
    loaded from the database into berkeley cache. The
    application fails in db->put function while loading
    the objects. This segmentation fault error is not
    consistently occuring every time on the same object.Also indicative of typical misuse of heap, pointer errors, or otherwise undefined behavior on the application's part.
    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 182927004352 (LWP 14638)]
    0x0000002a9643203a in __db_check_txn () from
    /opt/home/pesprm/local/db-4.6.19/db-4.6.19/build_unix/
    .libs/libdb-4.6.so
    (gdb) where
    #0 0x0000002a9643203a in __db_check_txn () from
    /opt/home/pesprm/local/db-4.6.19/db-4.6.19/build_unix/
    .libs/libdb-4.6.so
    #1 0x0000002a9643475b in __db_put_pp () from
    /opt/home/pesprm/local/db-4.6.19/db-4.6.19/build_unix/
    .libs/libdb-4.6.so
    #2 0x000000000043586b in
    esp::BerkeleyCache::insert_i (this=0x7fbfffe380,
    transactionId=866640768, pObj=0x7fbfffd3e0) at
    BerkeleyCache.cpp:838
    #3 0x00000000004119c5 in RefServer::loadObject
    (this=0x7fbfffdbe0, objInfo=<value optimized out>,
    strPrimaryObjName=@0x7fbfffd6f0,
    procParams=<value optimized out>) at
    BerkeleyCache.h:569
    4 0x0000000000419166 in RefServer::loadObjects
    (this=0x7fbfffdbe0) at RefServer.cpp:579
    #5 0x0000000000419748 in main (argc=<value optimized
    out>, argv=<value optimized out>) at
    RefServer.cpp:296Did you build the libraries stripped or otherwise remove debugging information?
    run "file /opt/home/pesprm/local/db-4.6.19/db-4.6.19/build_unix/.libs/libdb-4.6.so"
    Also, if I'm not mistaken this is Linux you're porting to, right? Might want to drop the "/opt" Solaris-ism as you continue to port more to Linux.
    The code that calls the db->put() function is given
    below:
         if (pTable->getDataOffset() == -1)Does this return an unsigned or signed value?
    pTable->setDataOffset(
    t( (int)(pObj->getDataBufferStartPos() -
    pObj->getDataStartPos()) );You cast to int here, what's the background reasoning for it?
         DB* pdb = pTable->getDB();
         int rc = 0;You don't check pdb is valid.
    Synchronize
    e sync(pPrimaryKey->getKeyBufferCriticalSection());
    pPrimaryKey->getKeyValues(pObj,
    , pPrimaryKey->getKeyBuffer());
         DBT key, data;
         memset(&key, 0, sizeof(DBT));
         key.flags = DB_DBT_USERMEM;
    key.data =
    = (void*)pPrimaryKey->getKeyBuffer().getBuffer();Do you verify this is even valid? Have you also checked the code within a debugger and verified the logic is correct?
    key.ulen = key.size =
    = pPrimaryKey->getKeyBuffer().getBufferLength();Same thing.
         memset(&data, 0, sizeof(DBT));
         data.flags = DB_DBT_USERMEM;
         if (pTable->isPrimaryDb())
              data.data = (void*)pObj->getDataBufferStartPos();
              data.ulen = data.size = pObj->getDataBufferSize();How do we know these are even valid? You're coming from the perspective that your code makes no mistakes when I have a hunch it does.
    rc = pdb->put(pdb, (DB_TXN*)transactionId, &key,
    y, &data, DB_NOOVERWRITE);Right, and this will most definitely result in a segmentation violation if you don't pass it valid data.
    You're on Linux, I highly suggest you download and build Valgrind, run your application w/ valgrind --tool=memcheck, and get back to us. Also, don't strip debugging information from the berkeley db libraries during this phase of troubleshooting - especially when you're still porting something over.
    I have tried using the BDB versions
    4.5.20/4.6.18/4.6.19 with the application and it
    throws segmentation fault error with all versions of
    BDB.Because the issue isn't within BDB.
    We are using the Sybase Adaptive DB server running in
    Solaris/Linux servers. The same application that
    runs in Solaris connecting to Sybase DB (in solaris)
    is working perfectly fine.More correctly, it was working perfectly fine under Solaris. That doesn't even mean that it's not taking part in undefined behavior - it just means it "worked."

  • How can I use syscall() from 32-bit application in 64-bit Solaris (v. 5.8)

    Solaris 5.8
    Sun Blade 150 (64-bit)
    I have got SYGSYS when call syscall(...) from my 32-bit application.
    Is it possible to use syscall() in 32-bit applications under 64-bit Solaris?

    Hello again.
    You may use the debugger (mdb) to open the core file generated by the SIGSYS trap:mdb coreThen you type::regs to list the register values at the time of the trap (in hexadecimal form).
    For Sparc machines (it is more complicated on x86 machines) g1 holds the system call number, o0 holds the first argument, o1 the second one ... o5 the 6th one. (For system calls with more than 6 arguments the 7th, 8th... argument are stored on the stack.)
    If g1 is 0 you know that the system call is done indirectly using SYS_syscall so the arguments are shifted (see above) and o0 holds the system call number.
    You can exit mdb using::quitMartin

  • Can I use Solaris with my Home Recording Studio?

    Hello,
    I am currently building a basic home recording studio. I recently assembled a new computer and will be purchasing music recording equipment very soon. Before I purchase the audio recording gear, I was curious about a few things pertaining to the use of Solaris as my possible choice system.
    The data that I store on my hard drives will need to be secure. I had originally considered RAID 5 though recently found out about RAID Z, which appears to be far ahead of the other RAIDs. I am curious to know more about how to set up a RAID Z system.
    The computer will be running Solaris, various Linux or BSD, and Windows Vista. I have 500GB x4 hard drives. I am considering separating one and using it strictly for Vista, and using the remaining 3 with a RAID set-up for nix. If I had a choice, I would put much less hard drive space into Vista (capping it at 150 to 200 GB), though I have yet to come across a RAID system that effectively or efficiently cooperates cross-platform. With that in mind, the majority of the remaining 1.5TB can go into my studio OS - hopefully Solaris - while left-over hard drive space is set aside for various other *nix.
    I've used Solaris 10 before, though haven't really gone into detail on the mechanics of such features as ZFS, zones, now RAID Z, and the many more amazing features that Solaris provides. Likewise, I am not really familiar with how well the system might operate with software/applications that I could use for recording and composing music.
    Beyond the available 2TB (or 1.5TB RAID-ready) space, my computer is running on a new 64-bit quad-core AMD CPU (~2.6GHz) and currently has 4GB 1066MHz RAM. In my search for preparing a computer that suits me for high performance recording - including the editing and mastering of audio - I am attempting to narrow down my options on the software side of things. I have been very satisfied with the general file management of Solaris, though am unsure of how well it might run as the software side of a home recording studio. An additional factor in deciding will be the software's compatbility with audio PCI cards and external recording/audio interfaces. There is always a question of whether or not the necessary drivers, firmware, or similar is available between any given hardware and software components.
    Some other *nix options I have considered - "Ubuntu Studio 64-bit" (though it appears to prefer 32-bit) and "64 Studio" (also Debian-based, though appears to be optimized for 64-bit). Some colleagues have used Gentoo with studio applications, though I don't know of any Linux distributions that offer the versatility, power, stability, and efficiency of Solaris for the operating system that it is.
    If I use something like "64 Studio", I will have the advantage of a system that is ready-built for studio recording purposes as well as a system that I know is compatible with the sound gear that I am considering purchasing. However, those systems are restricted by their file system types, RAID availability and dependability, and the general disadvantages of using the Linux kernel in general. (I enjoy Linux, though I admittedly prefer Unix over it.)
    Can I use Solaris with my home recording studio?
    Thank you!
    Edited by: the_professor on Nov 9, 2008 6:26 PM
    Corrected a typo.
    Edited by: the_professor on Nov 9, 2008 6:30 PM
    Caught another typo.

    I'm not sure what your question is. If you have particular software you want to run, you should see what you can get that package to run under. Sound hw stuff don't tend to be too portable unless it's written on top of OSS (htttp://www.opensound.com). Were I you, I'd consider separating out the storage part and the processing part. Get something like a cheap dell sc440 to be a file server and give the drives to that (unless you actually can get all the components working under solaris).
    -r

  • Server dumps core

    we run WLS7.0 SP4 on Sun Solaris with -server option, but the server dumps core
    once in a while. Can anyone help on this? Thanks a lot
    Shiye Qiu

    My "solution" doesn't change your architecture at all.
    Your web servers are showing a stack trace pointing to libpassthrough.so. This is a shared object that runs in the Web Server. I'm suggesting that rather than use an old libpassthrough.so that may (or may not) have problems, try using the built-in Reverse Proxy feature of Web Server. The Reverse Proxy feature is derived from the older libpassthrough.so, but has had many enhancements over the years. It IS a newer version of the load balancer shared object you are currently using.

  • Dual OS system booting issue - Solaris with Windows XP Pro

    Hi,
    I have installed Windows XP Professional with SP2 on my laptop Dell Inspiron 6400 (Intel Core 2 Duo). I created partition as below,
    C: 25GB (Primary : Active) Installed XP
    D: 15GB (Primary) - Tried to install Solaris here
    F: 10GB (Primary)
    G: 20 GB (Logical)
    H: 20 GB (Logical)
    1. I tried to install Solaris 10, booted up system from DVD and selected Solaris. I got a message related to "License..." and it stopped right there, nothing showed up on screen after the message. I forced it to shutdown.
    2. Next, I tried with Solaris Express Developer edition DVD. I was able to proceed until "Install" option. After clicking "Install" button, it reported some account name(no account name found) setting problem and quitted from installation. It asked to remove the DVD manually. But I was not able to eject it, got stuck. I switched off it and removed DVD.
    When I bootup the system next time from HDD or CD or USB bootable backup, it showed blank screen and blinking cursor. I am not able to boot system with Win XP or USB Win Xp bootable. I am able to enter BIOS setup.
    Please let me know how to boot up Win Xp and install Solaris with it.

    with my little experience i find solaris 10 isn't able to install on sata hdd but with solaris express edition 5.11 i was able to install it on my lap top toshiba tecra and now i can boot with xp sp2 and solaris i hope this answer your question .

Maybe you are looking for

  • How do i transmit shared libraries from one computer to apple tv?

    how do i transmit shared libraries from one computer to my apple TV?

  • Ipod output won't play on right side

    anything my ipod is plugged into from the top output jack will not play on the right side. tape adapter, headphones... blah blah blah. should i pay to get this repaired? it used to work on both sides if the ipod was pressed very firmly around the top

  • Oracle tags in templates

    I know I've seen posts on this in the past, but can't find them for the life of me. I've searched through about 20 pages of search results with no hits, so I must ask again. Can someone explain why the functionality of the oracle tags were removed fr

  • Missing Pacific Sales Points

    Hello,  We made a purchase of LG Wahser and Dryer on August 17, 2014 with delivery I believe was August 22, 2014. We have yet to receive points for this purchase of about $1200 Sales #5430165

  • Exporting pdf to open on a PC

    Hi all, I wonder what program on the 'dark side' I can use to see shadows and alpha channels that I create in Pages....would Acrobat Pro do the job? Cheers Chris. p.s. I have read a lot about PDF-X but would rather not compress the files.