Re: [DynInst_API:] Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion `!"WARNING: overlapping try blocks\n"' failed.

2018-05-14 Thread Jim Galarowicz

Hi Sasha,

Thanks!   I will build with the branch and have the user test again.

Thanks,

Jim G


On 05/14/2018 01:47 PM, Sasha Da Rocha Pinheiro wrote:


Hi Jim,


we are trying to fix this issue. There is already a fix related to try 
blocks but it's not in the master branch, nor it has been tested yet.


Meanwhile, you may want to merge this commit locally and see if it 
fixes your problem. It's in the branch sasha/fix-eh-frame-parse.



I will test it and possibly merge to master but without further data I 
can't tell if it fixed your issue.


Let us know if you have any success.


Regards,

Sasha


*From:* Dyninst-api  on behalf of 
Xiaozhu Meng 

*Sent:* Wednesday, May 9, 2018 5:29:58 PM
*To:* Jim Galarowicz
*Cc:* Don Maghrak; dyninst-api@cs.wisc.edu
*Subject:* Re: [DynInst_API:] 
Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion 
`!"WARNING: overlapping try blocks\n"' failed.

Hi Jim,

In theory, try blocks should not overlap because otherwise how we know 
which catch block to handle the exception happened at the overlapping 
address.


So, it is more likely that there is a problem with the eh_frame 
parsing, which leads to wrong try block ranges.


For debugging, can you ask the user to run

objdump --dwarf=frames-interp PATH_TO_THE_TARGET

and sends us the output?

This command should output the correct exception handling information. 
We can then determine whether there is indeed overlapping try blocks 
or the parsing of try blocks is wrong.


Thanks,

--Xiaozhu





On Wed, May 9, 2018 at 3:06 PM, Jim Galarowicz > wrote:


Hi all,

We have an abort that is showing a
Assertion `!"WARNING: overlapping try blocks\n"' failed. from
Dyninst.//
//The user stated that no core file was dropped.//

//The code is protected, so we don't have source code access or
execution access other than through the user.
Can anyone shed any light on what might cause overlapping try
block assertion?
This OSS version was built with a Nov 28, 2107 version of Dyninst.

Thanks,
Jim G


/
Processing raw data for alegra_3D_opt_team_tlcc2.x .../
/Processing processes and threads .../
/Processing performance data .../
/Processing symbols .../
/Resolving symbols for
/gpfs1/swbova/Alegra/trunk/bin/alegra_3D_opt_team_tlcc2.x/
/osscollect:

/projects/OpenSpeedShop/jgalaro/openspeedshop-externals/BUILD/ghost-login3/dyninst-20171128/parseAPI/src/SymtabCodeSource.C:549:
void Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks():
Assertion `!"WARNING: overlapping try blocks\n"' failed./
//projects/OSS/cts1/osscbtf_v2.3.1.u3b.debug/bin/osspcsamp: line
1781: 98255 Aborted osscollect $topology_opt $cbtf_offline_opt
--program "$1" --collector $collector

/The application was built with these module enabled:

intel/17.0 gcc/4.9.3 openmpi-intel/1.10

with lines like this:

/mpicxx -std=c++0x -O2 -axAVX -fp-model strict -ftz -diag-disable
15009 -g …/
/mpif90 -O2 -axAVX -fp-model strict -ftz -diag-disable 15009 …/
/mpif77 -O2 -axAVX -fp-model strict -ftz -diag-disable 15009 …/

the link line is

/mpicxx -std=c++0x -O2 -axAVX -fp-model strict -ftz -diag-disable
15009    -o alegra_3D_opt_team_tlcc2.x.tmp Alegra/team/alegra.o
Alegra/team/Code_Coupling_Client.o Alegra/team/build_info.o
-L/gpfs1/swbova/Alegra/trunk/lib/3D_opt_team_tlcc2
-L/projects/alegra/TPL/CavityExpansion/1.0b/lib/opt_tlcc2
-L/projects/alegra/TPL/LegacyContact/1.0-n3/lib/opt_tlcc2
-L/projects/alegra/TPL/xyce/6.7/inst_opt_tlcc2/lib
-L/projects/alegra/TPL/sundials/2.6.1/install_opt_tlcc2/lib
-L/projects/alegra/TPL/spice/1.1-n1/lib/opt_tlcc2
-L/projects/alegra/TPL/lambda/0.2.13/lib/opt_tlcc2
-L/projects/alegra/TPL/gnom3-fe/1.0.0/lib/opt_tlcc2
-L/projects/alegra/TPL/pff/2.1-n1/lib/opt_tlcc2
-L/projects/alegra/TPL/dakota/6.6/inst_opt_tlcc2/lib
-L/projects/alegra/TPL/acme/2.6c-n21/lib/opt_tlcc2 -L.
-L/projects/alegra/TPL/mesquite/0.9.6-n7/lib/opt_tlcc2
-L/projects/alegra/TPL/aprepro/2014_09_14/lib/opt_tlcc2
-L/projects/alegra/TPL/trilinos/2017_05_15/inst_opt_tlcc2/lib
-L/projects/alegra/TPL/parmetis/4.0.3/inst_opt_tlcc2/lib
-L/projects/alegra/TPL/sculpt/15.4b-n9/lib/opt_tlcc2
-L/projects/alegra/TPL/diom_spy/2.9/lib/opt_tlcc2
-L/projects/alegra/TPL/umfpack/5.1/inst_opt_tlcc2/lib
-L/projects/alegra/TPL/y12m/1.0/lib/opt_tlcc2
-L/projects/alegra/TPL/freetype/1.3.1/lib/opt_tlcc2
-L/projects/alegra/TPL/slang/1.0/lib/opt_tlcc2
-L/projects/alegra/TPL/jpeg/6b_27-Mar-1998/lib/opt_tlcc2
-L/projects/alegra/TPL/image/2.4/lib/opt_tlcc2
-L/projects/alegra/TPL/mesaaux/3.2.1/lib/opt_tlcc2
-L/projects/alegra/TPL/superludist/2.0/lib/opt_tlcc2

Re: [DynInst_API:] Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion `!"WARNING: overlapping try blocks\n"' failed.

2018-05-14 Thread Sasha Da Rocha Pinheiro
Hi Jim,


we are trying to fix this issue. There is already a fix related to try blocks 
but it's not in the master branch, nor it has been tested yet.

Meanwhile, you may want to merge this commit locally and see if it fixes your 
problem. It's in the branch sasha/fix-eh-frame-parse.


I will test it and possibly merge to master but without further data I can't 
tell if it fixed your issue.

Let us know if you have any success.


Regards,

Sasha


From: Dyninst-api  on behalf of Xiaozhu Meng 

Sent: Wednesday, May 9, 2018 5:29:58 PM
To: Jim Galarowicz
Cc: Don Maghrak; dyninst-api@cs.wisc.edu
Subject: Re: [DynInst_API:] 
Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion `!"WARNING: 
overlapping try blocks\n"' failed.

Hi Jim,

In theory, try blocks should not overlap because otherwise how we know which 
catch block to handle the exception happened at the overlapping address.

So, it is more likely that there is a problem with the eh_frame parsing, which 
leads to wrong try block ranges.

For debugging, can you ask the user to run

objdump --dwarf=frames-interp PATH_TO_THE_TARGET

and sends us the output?

This command should output the correct exception handling information. We can 
then determine whether there is indeed overlapping try blocks or the parsing of 
try blocks is wrong.

Thanks,

--Xiaozhu





On Wed, May 9, 2018 at 3:06 PM, Jim Galarowicz 
> wrote:
Hi all,

We have an abort that is showing a
Assertion `!"WARNING: overlapping try blocks\n"' failed. from Dyninst.
The user stated that no core file was dropped.

The code is protected, so we don't have source code access or execution access 
other than through the user.
Can anyone shed any light on what might cause overlapping try block assertion?
This OSS version was built with a Nov 28, 2107 version of Dyninst.

Thanks,
Jim G



Processing raw data for alegra_3D_opt_team_tlcc2.x ...
Processing processes and threads ...
Processing performance data ...
Processing symbols ...
Resolving symbols for /gpfs1/swbova/Alegra/trunk/bin/alegra_3D_opt_team_tlcc2.x
osscollect: 
/projects/OpenSpeedShop/jgalaro/openspeedshop-externals/BUILD/ghost-login3/dyninst-20171128/parseAPI/src/SymtabCodeSource.C:549:
 void Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion 
`!"WARNING: overlapping try blocks\n"' failed.
/projects/OSS/cts1/osscbtf_v2.3.1.u3b.debug/bin/osspcsamp: line 1781: 98255 
Aborted osscollect $topology_opt $cbtf_offline_opt --program 
"$1" --collector $collector

The application was built with these module enabled:

intel/17.0 gcc/4.9.3 openmpi-intel/1.10

with lines like this:

mpicxx -std=c++0x -O2 -axAVX -fp-model strict -ftz -diag-disable 15009 -g …
mpif90 -O2 -axAVX -fp-model strict -ftz -diag-disable 15009 …
mpif77 -O2 -axAVX -fp-model strict -ftz -diag-disable 15009 …

the link line is

mpicxx -std=c++0x -O2 -axAVX -fp-model strict -ftz -diag-disable 15009-o 
alegra_3D_opt_team_tlcc2.x.tmp Alegra/team/alegra.o 
Alegra/team/Code_Coupling_Client.o Alegra/team/build_info.o 
-L/gpfs1/swbova/Alegra/trunk/lib/3D_opt_team_tlcc2 
-L/projects/alegra/TPL/CavityExpansion/1.0b/lib/opt_tlcc2 
-L/projects/alegra/TPL/LegacyContact/1.0-n3/lib/opt_tlcc2 
-L/projects/alegra/TPL/xyce/6.7/inst_opt_tlcc2/lib 
-L/projects/alegra/TPL/sundials/2.6.1/install_opt_tlcc2/lib 
-L/projects/alegra/TPL/spice/1.1-n1/lib/opt_tlcc2 
-L/projects/alegra/TPL/lambda/0.2.13/lib/opt_tlcc2 
-L/projects/alegra/TPL/gnom3-fe/1.0.0/lib/opt_tlcc2 
-L/projects/alegra/TPL/pff/2.1-n1/lib/opt_tlcc2 
-L/projects/alegra/TPL/dakota/6.6/inst_opt_tlcc2/lib 
-L/projects/alegra/TPL/acme/2.6c-n21/lib/opt_tlcc2 -L. 
-L/projects/alegra/TPL/mesquite/0.9.6-n7/lib/opt_tlcc2 
-L/projects/alegra/TPL/aprepro/2014_09_14/lib/opt_tlcc2 
-L/projects/alegra/TPL/trilinos/2017_05_15/inst_opt_tlcc2/lib 
-L/projects/alegra/TPL/parmetis/4.0.3/inst_opt_tlcc2/lib 
-L/projects/alegra/TPL/sculpt/15.4b-n9/lib/opt_tlcc2 
-L/projects/alegra/TPL/diom_spy/2.9/lib/opt_tlcc2 
-L/projects/alegra/TPL/umfpack/5.1/inst_opt_tlcc2/lib 
-L/projects/alegra/TPL/y12m/1.0/lib/opt_tlcc2 
-L/projects/alegra/TPL/freetype/1.3.1/lib/opt_tlcc2 
-L/projects/alegra/TPL/slang/1.0/lib/opt_tlcc2 
-L/projects/alegra/TPL/jpeg/6b_27-Mar-1998/lib/opt_tlcc2 
-L/projects/alegra/TPL/image/2.4/lib/opt_tlcc2 
-L/projects/alegra/TPL/mesaaux/3.2.1/lib/opt_tlcc2 
-L/projects/alegra/TPL/superludist/2.0/lib/opt_tlcc2 
-L/projects/alegra/TPL/glu/3.2.1/lib/opt_tlcc2 
-L/projects/alegra/TPL/mesa/3.2.1/lib/opt_tlcc2 
-L/projects/alegra/TPL/nemesis/3.07-n3/lib/opt_tlcc2 
-L/projects/alegra/TPL/exodus/4.68-n1/lib/opt_tlcc2 
-L/projects/alegra/TPL/netcdf/4.3-snl1/inst_opt_tlcc2/lib -lutdem -lqsem 
-lremesh_app -lconduction -lremesh -ltnburn -lphysics -lmhd -lradiation 
-lkullimc -ltnburn -lphysics -lremap -linterface_recon -lremesh -lhedp_physics 
-lmhd -linterface_recon -lremap -lkullimc