Re: [ptp-user] sdm debugger: unable to determine gdb version

[Greg Watson <g.watson@xxxxxxxxxxxx>]

Hi Max,

This looks like a bug in the code to determine the GDB version. Please open a bug against 'Debug Core' here: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=PTP and I'll take a look.

Thanks,
Greg

On Dec 13, 2011, at 7:14 PM, Max wrote:

> Hi everybody,
> 
> I am struggling with a problem with the SDM debugger and I hope there
> is somebody around that could help me.
> 
> After downloading & unpacking the "Eclipse IDE for Parallel
> Application Developers", I started a new project (MPI Hello World) and
> I started to test PTP.. Unfortunately I was not able to start the
> parallel debugger, although the program runs w/o any glitches and all
> paths (according to the website) have been set. The error is as in the
> subject, and the full output is reported below, Google could not give
> any useful hint.
> 
> Program versions:
> 
> Eclipse IDE for Parallel Application Developers
> 
> Version: Indigo Service Release 1
> Build id: 20110916-0149
> 
> gdb --version
> GNU gdb (Gentoo 7.3.1 p1) 7.3.1
> 
> mpirun -V
> mpirun (Open MPI) 1.5.4
> 
> Report bugs to http://www.open-mpi.org/community/help/
> 
> Any idea?
> 
> Thanks
> Max
> 
> 
> 
> 
> Created sdm master runner.
> sdm master: command:
> [/home/myuser/Tmp/devel/eclipse/plugins/org.eclipse.ptp.linux.x86_64_5.0.2.201109141657/bin/sdm,
> --master, --port=41053, --host=192.168.0.3, --debugger=gdb-mi,
> --
> debugger_path=/home/myuser/Tmp/devel/eclipse/plugins/org.eclipse.ptp.linux.x86_64_5.0.2.201109141657/bin/sdm,
> --debug=127]
> sdm master: workdir: /home/myuser/workspace/helloWorld/Debug
> debug: Write routing file
> sdm master: associated to job #16777221
> sdm master: thread started.
> sdm master: waiting for SDM servers and front end.
> debug: waiting for connect
> sdm master: create process
> sdm master: changed state to RUNNING
> sdm master: waiting to finish
> sdm master: SDM: [0] effsize: 3, size: 2, rv: 0
> sdm master: SDM: [2] size 3
> sdm master: SDM: [2] route for 0 is {}
> sdm master: SDM: [2] route for 1 is {}
> sdm master: SDM: [2] in sdm_create_sockd_map
> sdm master: SDM: [2] sdm_route_get_route dest {0-2}, parent 2
> sdm master: SDM: [2] adjacent nodes: {0-1}
> sdm master: SDM: [2] adding 0 to my map
> sdm master: SDM: [2] adding 1 to my map
> sdm master: SDM: [2] effsize: 3, size: 2, rv: 0
> sdm master: SDM: [2] nodeID: 0, hostname: mytux, port: 52118
> sdm master: SDM: [2] Connection to child 0 successful
> sdm master: SDM: [2] nodeID: 1, hostname: mytux, port: 52474
> sdm master: SDM: [2] Connection to child 1 successful
> sdm master: SDM: [2] nodeID: 1, hostname: mytux, port: 52474
> sdm master: SDM: [2] Initialization successful
> sdm master: SDM: starting client
> sdm master: SDM: DbgMasterInit num_svrs=2
> sdm master: SDM: DbgMasterCreateSession host=192.168.0.3 port=41053
> Msg: EventRequestManager - addEventRequest(): Request: Start debugger
> request in status [UNKNOWN] for {0-1}.
> **** Msg: AbstractEventManager - registerEventRequest(): Request:
> Start debugger request in status [RUNNING] for {0-1}.
> SEND -> Worker-27
> sdm master: SDM:
> DbgMasterStartSession(helloWorld,/home/myuser/workspace/helloWorld/Debug,)
> sdm master: SDM: [2] Creating new request #0 expected replies {0-1}
> sdm master: SDM: [2] sdm_route_get_route dest {0-1}, parent 2
> sdm master: SDM: [2] sdm_message_send src {2} dest {0-1} route {0-1}
> sdm master: SDM: [2] Sending len 81
> sdm master: SDM: [2] Sending to 0
> sdm master: SDM: [2] About to send 85
> sdm master: SDM: [2] Sending to 1
> sdm master: SDM: [2] About to send 85
> sdm master: SDM: [2] About to call send_complete
> sdm master: SDM: [2] Leaving sdm_message_send
> sdm master: SDM: [2] receiving header
> sdm master: SDM: MESSAGE_LEN:71
> sdm master: SDM: [2] About to recv 71
> sdm master: SDM: [2] sdm_message_progress received len 71 from 1
> sdm master: SDM: [2] sdm_message_progress agg=0x1d59472 src={1} dest={2}
> sdm master: SDM: [2] About to call recv_callback
> sdm master: SDM: [2] Enter recv_callback
> sdm master: SDM: [2] got upstream message src={1}, dest={2}
> sdm master: SDM: [2] sdm_aggregate_message: upstream message #0 from {1}
> sdm master: SDM: [2] reply updated: src={1} replies outstanding: {0}
> sdm master: SDM: [2] creating new reply #1d59472 for request 0
> sdm master: SDM: [2] Leaving recv_callback
> sdm master: SDM: [2] Finished recv_callback
> sdm master: SDM: [2] receiving header
> sdm master: SDM: MESSAGE_LEN:71
> RECEIVE:[65] -> Proxy Client Packet Thread
> sdm master: SDM: [2] About to recv 71
> sdm master: SDM: [2] sdm_message_progress received len 71 from 0
> sdm master: SDM: [2] sdm_message_progress agg=0x1d59472 src={0} dest={2}
> sdm master: SDM: [2] About to call recv_callback
> sdm master: SDM: [2] Enter recv_callback
> sdm master: SDM: [2] got upstream message src={0}, dest={2}
> sdm master: SDM: [2] sdm_aggregate_message: upstream message #0 from {0}
> sdm master: SDM: [2] reply updated: src={0} replies outstanding: {}
> sdm master: SDM: [2] updating reply #1d59472 with src {0} for request 0
> sdm master: SDM: [2] Leaving recv_callback
> **** Msg: AbstractEventManager - notifyEventRequest(): Request: Start
> debugger request in status [DONE] for {}.sdm master: SDM: [2] Finished
> recv_callback
> 
> sdm master: SDM: [2] request 0 completed for #1d59472
> sdm master: SDM: dbg_master_cmd_completed src={0-1}Msg: NotifyJob -
> size of runnables: 4
> 
> sdm master: SDM: [2] Enter free_request
> sdm master: SDM: [2] Leaving free_request
> Msg: EventRequestManager - addEventRequest(): Request: Stop debugger
> request in status [UNKNOWN] for {}.
> SEND -> Worker-24
> sdm master: SDM: DbgMasterQuit()
> **** Msg: AbstractEventManager - notifyEventRequest(): Request: Stop
> debugger request in status [DONE] for {}.
> sdm master: SDM: [2] Creating new request #3 expected replies {0-1}
> sdm master: SDM: [2] sdm_route_get_route dest {0-1}, parent 2
> sdm master: SDM: [2] sdm_message_send src {2} dest {0-1} route {0-1}
> sdm master: SDM: [2] Sending len 14
> sdm master: SDM: [2] Sending to 0
> sdm master: SDM: [2] About to send 18
> sdm master: SDM: [2] Sending to 1
> sdm master: SDM: [2] About to send 18
> sdm master: SDM: [2] About to call send_complete
> sdm master: SDM: [2] Leaving sdm_message_send
> sdm master: SDM: shutdown completed
> sdm master: SDM: DbgMasterFinish
> sdm master: SDM: all finished
> sdm master: SDM: [2] receiving header
> sdm master: SDM: MESSAGE_LEN:18
> sdm master: SDM: [2] About to recv 18
> sdm master: SDM: [2] sdm_message_progress received len 18 from 1
> sdm master: SDM: [2] sdm_message_progress agg=0x3dde9765 src={1} dest={2}
> sdm master: SDM: [2] About to call recv_callback
> sdm master: SDM: [2] Enter recv_callback
> sdm master: SDM: [2] got upstream message src={1}, dest={2}
> sdm master: SDM: [2] sdm_aggregate_message: upstream message #3 from {1}
> sdm master: SDM: [2] reply updated: src={1} replies outstanding: {0}
> sdm master: SDM: [2] creating new reply #3dde9765 for request 3
> sdm master: SDM: [2] Leaving recv_callback
> sdm master: SDM: [2] Finished recv_callback
> sdm master: SDM: [2] receiving header
> sdm master: SDM: [2] Error retrieving message size!
> sdm master: exit value 0
> sdm master: changed state to FINISHED
> sdm master: thread finished
> _______________________________________________
> ptp-user mailing list
> ptp-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-user