Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327302 - SDM crashes when debugging Fortran program on 32bit linux
Summary: SDM crashes when debugging Fortran program on 32bit linux
Status: CLOSED DUPLICATE of bug 332394
Alias: None
Product: PTP
Classification: Tools
Component: Debug SDM (show other bugs)
Version: 4.0.3   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-08 02:57 EDT by Bala CLA
Modified: 2017-06-23 00:33 EDT (History)
1 user (show)

See Also:


Attachments
stacktrace of sdm (4.90 KB, text/plain)
2010-10-08 02:57 EDT, Bala CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bala CLA 2010-10-08 02:57:02 EDT
Build Identifier: 20100917-0705

While try to debug a simple MPI fortran hello world program, the SDM crashes with the following message:
*** glibc detected *** /home/bala/SW/eclipse/plugins/org.eclipse.ptp.linux.x86_4.0.3.201009162109/bin/sdm: munmap_chunk(): invalid pointer: 0x08071ac6 ***

The .metadata/.log does not any relevant java traces. 

The complete sdm stacktrace is attached at the end of this message.

Configuration:
My helios configuration looks like
CDT Helios Service Release 1
Build id: 20100917-0705
PTP version 4.0.3 (faced the same problem with 4.0.0 as well)
Photran 6.0.0

OS: 32 bit linux variants on VM
1. 2.6.32-21-generic #32-Ubuntu i686 
2. Fedora13 1686    
I am going to try this on 64bit machines also.


Reproducible: Always

Steps to Reproduce:
1. 32bit ubuntu (mint) or fedora13 OS
2. Just try debugging the demo hello mpi program using SDM
Comment 1 Bala CLA 2010-10-08 02:57:54 EDT
Created attachment 180471 [details]
stacktrace of sdm
Comment 2 Bala CLA 2010-10-08 03:13:15 EDT
Hi,

Just forgot to mention that i am using gnu fortran 4.4.x and openmpi version 1.4.3

Bala
Comment 3 Greg Watson CLA 2017-06-23 00:33:30 EDT

*** This bug has been marked as a duplicate of bug 332394 ***