Mailing List ArchivesAuthenticated access |
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesAuthenticated access |
|
| Date: | Wed, 09 May 2018 17:29:58 -0500 |
|---|---|
| From: | Xiaozhu Meng <mxz297@xxxxxxxxx> |
| 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 <jeg@xxxxxxxxxxxxx> wrote:
|
| [← Prev in Thread] | Current Thread | [Next in Thread→] |
|---|---|---|
| ||
| Previous by Date: | [DynInst_API:] [dyninst/dyninst] c4914b: 1. Add more non-returning functions, Xiaozhu Meng |
|---|---|
| Next by Date: | Re: [DynInst_API:] Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion `!"WARNING: overlapping try blocks\n"' failed., Jim Galarowicz |
| Previous by Thread: | [DynInst_API:] Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion `!"WARNING: overlapping try blocks\n"' failed., Jim Galarowicz |
| Next by Thread: | Re: [DynInst_API:] Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion `!"WARNING: overlapping try blocks\n"' failed., Jim Galarowicz |
| Indexes: | [Date] [Thread] |