This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Script ?
- To: insight at sources dot redhat dot com
- Subject: Script ?
- From: Jean-Baptiste Cazier <jcazier at decode dot is>
- Date: Mon, 1 Oct 2001 13:51:22 +0000
- Organization: Decode Genetics Inc.
- Reply-To: jcazier at decode dot is
Hi !
I have installed insight on top of gdb on my RH7.1 box.
I want to debug an MPI program which is started via the mpirun script. With
non default gdb it worked fine, but with insight it does not work anymore:
A normal call is "mpirun -np 2 exe opt"
mpirun: script
-np 2: number of processor
exe: executable
opt: optionfile
To debug my program I run
mpirun -np 2 -gdb exe opt
-gdb use gdb to debug
with the default gdb, gdb starts as soon as an error occur.
with insight gdb, i get an window opeing with the following error:
Warning
! Program received signal SIGUSR1, User defined signal 1
Don't show this warning again
OK
I click Ok and nothing happens !
The error to launch the debugger is
p1_30865: p4_error: interrupt SIGSEGV: 11
rm_l_1_30869: p4_error: interrupt SIGINT: 2
net_recv failed for fd = 8
bm_list_27063: p4_error: net_recv read, errno = : 104
[lws1] ~/devel/allegro/mpi/lws1 $
What can I do to start insight when an erro occur ?
Is it possible to start from inside insight ?
Thanks
Jean-Baptiste