On Mon, Oct 10, 2011 at 9:00 PM, Camaleón
<noelamac@gmail.com> wrote:
On Sun, 09 Oct 2011 23:44:00 +0800, lina wrote:
> I met "Segmentation fault" in two places in one day,
What are those places?
Hi,
On laptop, later I figured out due to the recent update of one package which cause its crashed.
after downgrading, it's fixed.
Another segmental fault is on cluster:
mpirun noticed that process rank 17 with PID 12834 on node c10 exited
on signal 11 (Segmentation fault).
(I guess this problem will keep it as it is. don't wanna trouble the administrator, but if you have suggestions welcome to let me know)
Crystal balls are expensive :-)
Ha ... I am your crystal ball now, ask me more if you want. and ... and .. it's free!!!
(a bit kidding here, sorry I should have provided more info. before)
> Which are the possible reasons for the segmentation fault.
Wow, there can be many. You need to provide more data.'
I choose some which I thought might be important data.
Signal: Segmentation fault (11)
Signal code: Address not mapped (1)
Failing at address: 0xd1
[ 0] /lib64/libpthread.so.0 [0x3ec8e0e7c0]
[ 1] /usr/local/mpi/intel/lib/openmpi/mca_pml_ob1.so [0x2b7c80a013e8]
:
:
[14] /lib64/libc.so.6(__libc_start_main+0xf4) [0x3ec861d994]
[15] mdrun_mpi_d(do_cg+0x1c1) [0x40b359]
Thanks,
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] pan.2011.10.10.13.00.53@gmail.com" target="_blank">http://lists.debian.org/[🔎] pan.2011.10.10.13.00.53@gmail.com