iaozhu Meng <mxz...@gmail.com>
*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.
@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 th
t: 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
Hi Xiaozhu,
I've sent the user a request.
Thanks much for the reply!
Jim G
On 05/09/2018 05:29 PM, Xiaozhu Meng wrote:
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
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
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
