LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: v.kuznetsov_at_[hidden]
Date: 2005-11-21 12:31:44


Hi again,
1. I compiled laminfo with debugging info:
g++ -g -O3 -o laminfo laminfo.o -pthread ../../share/libmpi/.libs/libmpi.a
../../share/liblam/.libs/liblam.a -lutil
2. ran it with a breakpoint to call of first function:
less laminfo.cc:
  // Initialize the argv parsing handle

  ad = ao_init();

ATB# gdb /usr/local/bin/laminfo
GNU gdb 4.18 (FreeBSD)
-------------

(gdb) break ao_init
Breakpoint 1 at 0x8090bde
(gdb) run
Starting program: /usr/local/bin/laminfo
[hangs]...
^C
Program received signal SIGINT, Interrupt.
0x48197900 in __sys_poll () from /usr/lib/libc_r.so.4

So it even don't comes to first function ao_init!
3. I recompiled laminfo with one printf string before any action:
  bool want_all = false;
        printf("ffdfd\n");

  // Initialize the argv parsing handle

Ran it and it hangs too.
4. simple "hello" C and c++ compiles and runs without problem.

May be I simply gives you access to this freebsd box? If you send me your
PGP key I'd be glad to make you an account to this box.
        Thank you,
                Vassili
        

> -----Original Message-----
> From: lam-bounces_at_[hidden] [mailto:lam-bounces_at_[hidden]] On Behalf
> Of Jeff Squyres
> Sent: Monday, November 21, 2005 7:04 PM
> To: General LAM/MPI mailing list
> Subject: Re: LAM: FW: FreeBSD MPI_INIT problem
>
> Based on your stack trace, it looks like something is getting
> corrupted. Unfortunately, I do not have access to any FreeBSD machines
> to test this myself. However, laminfo is clearly not getting very far
> -- can you step/next through from the beginning of the program to see
> where exactly it is failing?
>