Conference turris::decladebug

865.0. "SEGV when running ladebug" by MPGS::WHITNEY (Bill Whitney - New Media Solutions DTN 237-3859) Tue Mar 04 1997 16:19

    I'm having difficulty with ladebug (4.0-30) on some programs.  When I
    execute the program, I immediately get a SEGV. The program works fine
    with dbx.  This is threaded application that links with Oracle OCI
    shared libraries.
    
    Any ideas on what is happening?
    
    Thanks, Bill
    
    
    [jazmin:/dvs/bss]> ladbx BEEserver
    Welcome to the Ladebug Debugger Version 4.0-30
    ------------------ 
    object file name: BEEserver 
    Reading symbolic information ...done
    (ladebug) run -delay 0
    Thread received signal SEGV
    pc address 0x3ff00000004 is invalid; substituting RA
    stopped at [ 0x3ff00000006]
    (ladebug) q
    [jazmin:/dvs/bss]> dbx BEEserver
    dbx version 3.11.10
    Type 'help' for help.
    
    main: 295  char * root_dir="/tmp";    
    (dbx) run -delay 0
            BEE - Broadcast Event Executer
            Copyright (c) Digital Equipment Corporation 1997.  All rights
    reserved.
            Version V2.3A, 03-MAR-97
    
    BEEserver -delay 0 
    
    Application registered ...
    
    

Which os version are you on?  Which decthread library are you using?
Do you use a special kernel?

I have just seen something earlier with PC address like this and it
was caused by a problem in DECthread library and kernel.   I am not
saying this will be the case, but we should check this out.

Wanfang

    This is on V4.0B, standard kernel but with a patched DECthreads shared
    library from the 'mega-patch' kit delivered by the DECthreads group.
    
    Bill (DTN 237-3859)
    

I just talked with Bill on the phone.  He will be working with
DECthread group on this issue.

Wanfang