Re: attaching gdb to restarted process

From: Richard Hu (rhu_at_opnet_dot_com)
Date: Thu Feb 16 2006 - 14:51:02 PST

  • Next message: Richard Hu: "Re: attaching gdb to restarted process"
    Hi Paul,
    Yes, this problem is consistent and I am able to attack fine to the same 
    executable pre-checkpoint.
    Basically, normally when you attach gdb to a process, it dynamically loads 
    the shared libraries necessary for the program.  It searches for symbols 
    for breakpoints, etc.  However, when I restart from a checkpoint and I 
    attach to that process - none of the loading is done.  In addition, when I 
    type "where" in gdb - I get a bunch of question marks where the function 
    names would normally be.
    At 05:44 PM 2/16/2006, you wrote:
    >   I am afraid we at LBNL don't have any experience w/ attaching gdb to
    >restarted processes.  However, if you consistently are unable to see
    >symbols or libs, then it probably is something we should open a bug
    >report for.  Is it a problem you *always* see or an intermitent one?
    >Are you able to attach OK to the same executable pre-checkpoint?
    >Richard Hu wrote:
    > > Hi,
    > >
    > > I was wondering if you have ever run into an issue where a process is
    > > restarted via cr_restart and you attach gdb to the process but gdb
    > > does not load any of the symbols or the shared libraries or other
    > > related gdb issues?  If so, do you have any advice on how to work
    > > around them?
    > >
    > > In addition, do you have any advice in general in using gdb with
    > > restarted processes or any known issues?
    > >
    > > Thanks,
    > > Richard
    > >
    >Paul H. Hargrove                          PHHargrove_at_lbl_dot_gov
    >Future Technologies Group
    >HPC Research Department                   Tel: +1-510-495-2352
    >Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

  • Next message: Richard Hu: "Re: attaching gdb to restarted process"