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

2018-05-17 Thread Jim Galarowicz
:* 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 sho

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

2018-05-14 Thread Jim Galarowicz
ninst::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

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

2018-05-14 Thread Sasha Da Rocha Pinheiro
arowicz 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

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

2018-05-09 Thread Jim Galarowicz
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

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

2018-05-09 Thread Xiaozhu Meng
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