dbx debugging - SUN

This is a discussion on dbx debugging - SUN ; Hi, When I read a core file in dbx, and print the stack trace I get the addresses and not the values of the parameters. Why is that so? And how can I see the values in the addresses? Here ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: dbx debugging

  1. dbx debugging

    Hi,

    When I read a core file in dbx, and print the stack trace I get the
    addresses and not the values of the parameters. Why is that so? And how
    can I see the values in the addresses? Here is the stack trace:

    =>[1] strlen(0x0, 0x69636558, 0x330678, 0x7efefeff, 0x81010100, 0x8),
    at 0xfb2344e4
    [2] CORBA::string_dup(0x69636558, 0x0, 0x330668, 0xfbb4b554,
    0xfbacca80, 0x960), at 0xfb72f0e4
    [3]
    TAO_Bindings_Iterator,ACE_Equal_To,ACE_Null_Mutex>,ACE_Hash_Map_Entry
    >:opulate_binding(0x19177d8, 0x1938338, 0x0, 0x2c1, 0xffbfe944, 0x23494), at 0xfbad1144

    [4]
    TAO_Bindings_Iterator,ACE_Equal_To,ACE_Null_Mutex>,ACE_Hash_Map_Entry
    >::next_n(0x18da828, 0x64, 0xffbfe8d4, 0xfc, 0xfbb49520, 0x0), at 0xfbad1f40

    [5] POA_CosNaming::BindingIterator::next_n_skel(0xffbf ecc8,
    0x18da878, 0xffbfea18, 0xfbaf3f88, 0xfbb49474, 0x0), at 0xfbaf4070
    [6] TAO_ServantBase::synchronous_upcall_dispatch(0x18d a840,
    0xffbfecc8, 0xffbfea18, 0x18da878, 0xfbb49400, 0xfb97eb60), at
    0xfb97ec54
    [7] TAO_Object_Adapter::dispatch_servant(0x0, 0xffbfed34, 0xffbfecc8,
    0xffbfeaf4, 0x0, 0xc4), at 0xfb94e71c
    [8] TAO_Object_Adapter::dispatch(0x4eae8, 0xffbfed34, 0xffbfecc8,
    0xffbfebac, 0x3e118, 0x3ddb0), at 0xfb94f604
    [9] TAO_Adapter_Registry::dispatch(0x3df20, 0xffbfed34, 0xffbfecc8,
    0xffbfec14, 0x6c, 0x1), at 0xfb79fdac
    [10] TAO_Request_Dispatcher::dispatch(0x26c58, 0x3ddb0, 0xffbfecc8,
    0xffbfecb8, 0x3ddb0, 0xfb869984), at 0xfb7b1798
    [11] TAO_GIOP_Message_Base:rocess_request(0x1905348, 0x19185e8,
    0xffbfee28, 0xffbff068, 0x0, 0x1), at 0xfb6f4ccc
    [12] TAO_GIOP_Message_Base:rocess_request_message(0x1905348,
    0x19185e8, 0x18ca188, 0xffbff068, 0x33cdf0, 0x0), at 0xfb6f4694
    [13] TAO_Transport:rocess_parsed_messages(0x19185e8, 0x18ca188,
    0xffbff71c, 0x0, 0x0, 0x0), at 0xfb6e0f6c
    [14] TAO_Transport:rocess_queue_head(0x19185e8, 0xffbff71c, 0x324,
    0xfb869694, 0xfb860188, 0x0), at 0xfb6e1294
    [15] TAO_Transport::handle_input(0x19185e8, 0xffbff71c, 0x0, 0x1,
    0x187a2c, 0x2d94), at 0xfb6dfe50
    [16] TAO_Connection_Handler::handle_input_internal(0x0, 0xffffffff,
    0x1913808, 0x3ddb0, 0xfb6e5bb0, 0xfb6cc214), at 0xfb6e584c
    [17] TAO_Connection_Handler::handle_input_eh(0x19138a8, 0xffffffff,
    0x1913808, 0x0, 0x16bb58, 0x19185e8), at 0xfb6e56f0
    [18] ACE_Select_Reactor_Notify::dispatch_notify(0x4d9e0 , 0xffbff848,
    0xacb58, 0xfb5bbb50, 0xfb5b0e7c, 0xffffffff), at 0xfb5043c8
    [19] ACE_TP_Reactor::handle_notify_events(0x0, 0x20, 0xffbff920,
    0x20, 0x20, 0x0), at 0xfb505f6c
    [20] ACE_TP_Reactor::dispatch_i(0x0, 0x0, 0xffbff920, 0x0, 0x0, 0x0),
    at 0xfb505cc4
    [21] ACE_TP_Reactor::handle_events(0x4d240, 0x0, 0x0, 0xfb502940,
    0xfb8510e8, 0xffbff930), at 0xfb505b40
    [22] TAO_ORB_Core::run(0x3ddb0, 0x0, 0xfb5030cc, 0xfb5ba104, 0x23cf8,
    0x4), at 0xfb778cb4
    [23] TAO_Naming_Service::run(0xffbffadc, 0x5, 0xffbffb94, 0xfbbb3a7c,
    0xfffef9a0, 0xfffef748), at 0x11d5c
    [24] main(0x5, 0xffbffb94, 0xffbffbac, 0x22c00, 0x0, 0x0), at 0x11934


    Thanks.


  2. Re: dbx debugging

    In article <1145451355.004796.171560@t31g2000cwb.googlegroups. com>,
    wrote:
    >Hi,
    >
    >When I read a core file in dbx, and print the stack trace I get the
    >addresses and not the values of the parameters. Why is that so?


    Is executable compiled with the debugging option on ?

    Without debug info, which keeps track of the 'type' of parameters, all the
    debugger can display is actual parameter 'values' -- without any concept of
    how they're being used (aka what 'type' they are), there's no way to display
    'translated' output.

    > And how
    >can I see the values in the addresses?


    the above should be sufficient clue.

    > Here is the stack trace:


    [.. sneck ..]]



+ Reply to Thread