To follow up on this thread --
Now that 1.0 is out the door, I went back and implemented this prior
suggestion (about making it easier to launch Open MPI under debuggers
other than TotalView -- see original text below). This is only
implemented on the trunk, meaning that it will be in the 1.1
> My points here were that for at least some debuggers, a
> naming scheme is all they need, and we should be able to accommodate
> that.
Yes, it seems that some advanced "renaming scheme" will fit most of needs.
(I mean if it allows to customize not only debugger name & path, but also
cmd-line op
On Fri, 2005-10-21 at 12:41 +0400, Konstantin Karganov wrote:
> > You and Chris G. raise a good point -- another parallel debugger vendor
> > has contacted me about the same issue (their debugger does not have an
> > executable named "totalview").
> > <...>
> > Comments?
> Actually, the point is
> The question was merely how to do it: call "gdb orterun" and catch it
> somewhere on breakpoint or attach to orterun later or smth else.
Reply to myself:
# gdb orterun
(gdb) br MPIR_Breakpoint
(gdb) run
(gdb)
(gdb) detach
(gdb) exit
Am I right?
Best regards,
Konstantin.
> You and Chris G. raise a good point -- another parallel debugger vendor
> has contacted me about the same issue (their debugger does not have an
> executable named "totalview").
> <...>
> Comments?
Actually, the point is deeper than just a debugger naming question.
High-quality MPI implementat
On Thu, 2005-10-20 at 22:03 +0400, Konstantin Karganov wrote:
> > However, we're quite open to other approaches. Because of the nature of
> > our integration with a variety of different run-time environments, our
> > startup is not a shell script -- mpirun ("orterun" is its real name;
> > "mpirun"
Konstantin, Jeff,
> TotalView interface goes well, except that its details are hardcoded in
> the source of orte/tools/orterun (as you may guess I don't have the
> executable named "totalview", etc.). I'd like to know when and where do
> the functions from orterun/totalview.{h,c} get called,
> However, we're quite open to other approaches. Because of the nature of
> our integration with a variety of different run-time environments, our
> startup is not a shell script -- mpirun ("orterun" is its real name;
> "mpirun" is a sym link to orterun) is a compiled executable.
Surely, I saw th
On Thu, 2005-10-20 at 13:04 +0400, Konstantin Karganov wrote:
> I'm working on an MPI-debugger project and have questions on OpenMPI
> support for debugger tools. Any info or links to docs would be
> appreciated.
At the moment, we're sadly lacking in documentation (particularly
developer document
