Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353864

Summary:	SDM double free or corruption (out) problem
Product:	[Tools] PTP	Reporter:	Adam Peplinski <adamp>
Component:	Debug SDM	Assignee:	Greg Watson <g.watson>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	g.watson
Version:	5.0.1
Target Milestone:	5.0.2
Hardware:	PC
OS:	Linux
Whiteboard:

Description Adam Peplinski

2011-08-04 06:53:48 EDT

Build Identifier: 20110615-0604

SDM breakks during the debugging of an example MPI fortran PI calcuation program (mpi_pi_example) with the error message:
*** glibc detected *** /home/adam/src/eclipse/plugins/org.eclipse.ptp.linux.x86_64_5.0.0.201106140904/bin/sdm: double free or corruption (out): 0x000000000112d860 ***

/lib/libc.so.6(+0x71ad6)[0x7fdf07a50ad6]

/lib/libc.so.6(cfree+0x6c)[0x7fdf07a5584c]

/home/adam/src/eclipse/plugins/org.eclipse.ptp.linux.x86_64_5.0.0.201106140904/bin/sdm[0x427499]

/home/adam/src/eclipse/plugins/org.eclipse.ptp.linux.x86_64_5.0.0.201106140904/bin/sdm[0x417439]
...

It happens after step into subroutine calc_pi. Moreover variable view doesn't sow in the readable way the values or types of variables declared in the program (e.g. "my_rank"; value "cb" ). After stepping into calc_pi subroutine only names for my_rank and num_procs are visible (no local variable present) and the execution of process rank 0 stops. It seem to happen for parallel fortran program only,  and the variable view works correctly for simple MPI C program. However, I din't test subroutines in MPI C.

Reproducible: Always

Steps to Reproduce:
1. Build example MPI fortran PI calculation 
2. Run parallel debugger and check variable view 
3. step into calc_pi

Comment 1 Greg Watson

2011-08-04 07:58:22 EDT

What are the versions of the Fortran compiler and gdb?

Comment 2 Adam Peplinski

2011-08-04 10:29:08 EDT

(In reply to comment #1)
> What are the versions of the Fortran compiler and gdb?

Its debian 2.6.32-5-amd64
gfortran 4.4.5
gdb 7.0.1
I tested C version of this program and there are no problems

Comment 3 Greg Watson

2011-08-10 09:48:46 EDT

Debugger was not correctly recognizing GNU kind notation. This solves the immediate issue, but I don't think fortran types are fully implemented, so other problems may occur.