- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: setenv MPI_FLAGS eladebug - NOT working
Operating System - Tru64 Unix
1752777
Members
6359
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2004 09:02 AM
тАО04-13-2004 09:02 AM
setenv MPI_FLAGS eladebug - NOT working
One of our developers is having this problem.
We're still not at 100% capability with our tools on the Alpha because ladebug 4.69 does not listen to the set MPI_DEBUG_CONT=1
as it's supposed to, per the HP MPI 2.0 User's Guide.
Can anyoneshed some light on this?
P.S. NOTE that if we instead 'setenv MPI_FLAGS egdb' to use the gdb debugger, gdb *does* listen to that set command and proceed, but there are other aspects of gdb that we are not happy with...
-------------------detailed problem description:-------------------
If we do:
setenv MPI_FLAGS eladebug
mpirun -np 2
it fires off 2 ladebug xterms as it should, both stopping in MPI_INIT. You are supposed
to be able to then:
[set breakpoints as desired]
set MPI_DEBUG_CONT=1
continue
in each xterm to get it to proceed, but it doesn't like that 'set' command. I also tried it as an environment variable with no luck--we're just stuck in MPI_INIT.
We're still not at 100% capability with our tools on the Alpha because ladebug 4.69 does not listen to the set MPI_DEBUG_CONT=1
as it's supposed to, per the HP MPI 2.0 User's Guide.
Can anyoneshed some light on this?
P.S. NOTE that if we instead 'setenv MPI_FLAGS egdb' to use the gdb debugger, gdb *does* listen to that set command and proceed, but there are other aspects of gdb that we are not happy with...
-------------------detailed problem description:-------------------
If we do:
setenv MPI_FLAGS eladebug
mpirun -np 2
it fires off 2 ladebug xterms as it should, both stopping in MPI_INIT. You are supposed
to be able to then:
[set breakpoints as desired]
set MPI_DEBUG_CONT=1
continue
in each xterm to get it to proceed, but it doesn't like that 'set' command. I also tried it as an environment variable with no luck--we're just stuck in MPI_INIT.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2004 11:30 PM
тАО04-13-2004 11:30 PM
Re: setenv MPI_FLAGS eladebug - NOT working
Hi,
are you using csh?
greetings,
Michael
are you using csh?
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-14-2004 06:03 AM
тАО04-14-2004 06:03 AM
Re: setenv MPI_FLAGS eladebug - NOT working
>I have a response on the forum, they are asking if you are using 'csh'?
>
Yes--
also, I have tried
setenv MPI_DEBUG_CONT 1
once inside the xterms and that doesn't work either. The processes
won't budge past MPI_INIT. But doing
set MPI_DEBUG_CONT=1
using gdb *does* kick it loose. Ladebug says there is
no such variable when I try that.
>
Yes--
also, I have tried
setenv MPI_DEBUG_CONT 1
once inside the xterms and that doesn't work either. The processes
won't budge past MPI_INIT. But doing
set MPI_DEBUG_CONT=1
using gdb *does* kick it loose. Ladebug says there is
no such variable when I try that.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP