Problems with Socket

Santolo Felaco ahuramazda10 at
Thu Mar 12 09:19:14 CDT 2009

I execute ex42a and then ex42.


 mpirun -np 1 ./ex42a -start_in_debugger

(gdb) bt
#0  0xb7f9a410 in __kernel_vsyscall ()
#1  0xb7dd8c90 in nanosleep () from /lib/../lib/tls/i686/cmov/
#2  0xb7dd8ac7 in sleep () from /lib/../lib/tls/i686/cmov/
#3  0x08195837 in PetscSleep (s=10) at psleep.c:40
#4  0x081c277e in PetscAttachDebugger () at adebug.c:411
#5  0x081836a2 in PetscOptionsCheckInitial_Private () at init.c:371
#6  0x08187dfe in PetscInitialize (argc=0xbfb5edb0, args=0xbfb5edb4,
    help=0x8224da0 "Sends a PETSc vector to a socket connection, receives it
back, within a loop. Works with ex42.c.\n") at pinit.c:488
#7  0x0805073b in main (argc=2, args=0xbfb5ee34) at ex42a.c:17

mpirun -np 1 ./ex42 -start_in_debugger

(gdb) bt
#0  0xb7f8a410 in __kernel_vsyscall ()
#1  0xb7dc8c90 in nanosleep () from /lib/../lib/tls/i686/cmov/
#2  0xb7dc8ac7 in sleep () from /lib/../lib/tls/i686/cmov/
#3  0x081953d7 in PetscSleep (s=10) at psleep.c:40
#4  0x081c231e in PetscAttachDebugger () at adebug.c:411
#5  0x08183242 in PetscOptionsCheckInitial_Private () at init.c:371
#6  0x0818799e in PetscInitialize (argc=0xbfaded30, args=0xbfaded34,
    help=0x8223c00 "Reads a PETSc vector from a socket connection, then
sends it back within a loop. Works with ex42.m or ex42a.c\n") at pinit.c:488
#7  0x0805073b in main (argc=2, args=0xbfadedb4) at ex42.c:18

2009/3/12 Matthew Knepley <knepley at>

> On Thu, Mar 12, 2009 at 8:20 AM, Santolo Felaco <ahuramazda10 at>wrote:
>> Hi I use Petsc 2.3.1 (I don't use the last version because I work on a
>> software developed with this version).
>> I tried to used the Petsc socket, but the client and server programs but
>> they don't connect (the execution is blocked).
>> I am using two examples of Petsc:
>> I tried to execute ex42a on machine and ex42 on other machine, and I
>> execute both programs on same machine.
> 1) It is extremely hard to debug old code. We have made several socket
> fixes for new OS/architectures.
> 2) Make sure you start the server (ex42a) and then the client (ex42)
> 3) Run using the debugger, -start_in_debugger, and give us a stack trace of
> the hang
>   Matt
>> Do you help me? Thanks.
>> Bye.
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the petsc-users mailing list