> >> <
g.watson@xxxxxxxxxxxx>
> >>
> >> Fabio,
> >>
> >> I get virtually identical output to you up to the "don't know
> >> how to handle OS specific section" line, so it looks like this
> >> is causing the problem.
> >>
> >> Can you try the following:
> >>
> >> 1. Log into one of the nodes and run 'gdb myprog' where myprog
> >> is the MPI program you're trying to run.
> >> 2. Set a breakpoint in main using the command 'set breakpoint
> >> main'.
> >> 3. Start the program using 'run'.
> >>
> >> Let me know if you see any error messages or if gdb fails.
> >>
> >> Thanks,
> >>
> >> Greg
> >>
> >> On Jun 27, 2008, at 7:31 AM, Fabio Meneghini wrote:
> >> Hi Greg,
> >> first thanks for you helping me,
> >> BTW, the machine is a linux cluster, composed by 8
> >> single-processor computers interconnected, frontend
> >> included. Some moths ago I found that there was no gdb installed on the
> >> nodes, but only in the frontend (which is usually part of the
> >> computational nodes). So I copied the gdb binary from the frontend to
> >> the local folders on the other nodes. Now, when I access (through ssh or
> >> rsh) each node, I am able to run the gdb on that node, simply with the
> >> command /usr/bin/gdb
> >> So I suppose this might be ok.
> >>
> >> Regarding my citation: nevermind. Now, don't ask me
> >> why, the situation is somewhat different:
> >> First, as I start Eclipse, the following message
> >> appears in the terminal: "ORTE@Local: proxy
> >> connected"
> >> ok. That's awesome
> >>
> >> Then, it's time to start parallel debugging! then I
> >> launch the parallel debugger, with 8 processors,
> >> and: as the usual "Debugger has started...etc etc" window appears, it
> >> disappears almost instantly, and an error message raises up: "Handling
> >> debug Event....
> >> reason:
> >> See Details..."
> >> So I go to see the terminal, and the following
> >> results the output from the very moment I made the
> >> debugger run:
> >>
> >> debug: waiting for connect
> >> debug: received connected event
> >> Msg: EventRequestManager - addEventRequest():
> >> Request: Start debugger request in
> >> status [5] for 0-7.
> >> **** Msg: AbstractEventManager -
> >> registerEventRequest(): Request: Start debugger
> >> request in status [5] for 0-7.
> >> Msg: SDMEventManager - update(): Event:
> >> EVENT_DBG_OK transid=1 8:FF
> >> Msg: SDMEventManager - fireEvent(): added PDIEvent:
> >> org.eclipse.ptp.debug.intern
> >> al.core.pdi.event.ConnectedEvent@4365d26c
> >> Msg: NotifyJob - size of runnables: 3
> >> **** Msg: AbstractEventManager -
> >> notifyEventRequest(): Request: Start debugger r
> >> equest in status [3] for .
> >> Msg: NotifyJob - size of runnables: 3
> >> Msg: EventRequestManager - addEventRequest():
> >> Request: Set Function Breakpoint R
> >> equest in status [5] for 0-7.
> >> **** Msg: AbstractEventManager -
> >> registerEventRequest(): Request: Set Function B
> >> reakpoint Request in status [5] for 0-7.
> >> Msg: EventRequestManager - addEventRequest():
> >> Request: Resume request in status
> >> [5] for 0-7.
> >> Msg: SDMEventManager - update(): Event:
> >> EVENT_DBG_OK transid=1 8:FF
> >> **** Msg: AbstractEventManager -
> >> notifyEventRequest(): Request: Set Function Bre
> >> akpoint Request in status [3] for .
> >> **** Msg: AbstractEventManager -
> >> notifyEventRequest(): Request: Resume request i n
> >> status [3] for 0-7. Msg: NotifyJob - size of runnables: 5
> >> ================= TIME RESUME: 1214569632785
> >> ORTE@Local: BFD: /lib64/ld-linux-x86-64.so.2: don't
> >> know how to handle OS specif ic section `.gnu.hash'
> >> [0x6ffffff6] Msg: SDMEventManager - update(): Event:
> >> EVENT_DBG_EXIT transid=1 8:FF 177
> >> Msg: SDMEventManager - fireEvent(): added PDIEvent:
> >> org.eclipse.ptp.debug.intern
> >> al.core.pdi.event.DestroyedEvent@3bb505fe Msg: EventRequestManager -
> >> addEventRequest(): Request: Stop debugger request in status [5] for .
> >> Msg: SDMEventManager - fireEvent(): added PDIEvent:
> >> org.eclipse.ptp.debug.intern
> >> al.core.pdi.event.DisconnectedEvent@72282e3b **** Msg:
> >> AbstractEventManager -
> >> notifyEventRequest(): Request: Stop debugger re
> >> quest in status [3] for . calling session finish
> >> Msg: NotifyJob - size of runnables: 4
> >> debug: received disconnected event
> >> ORTE@Local: sdm: shutdown completed
> >>
> >>
> >> Any hints?
> >> thanks, again.
> >> Fabio
> >>
> >>
> >> 2008/6/27 Greg Watson