Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault when running Chrome with hextype #10

Open
YizhuoZhai opened this issue Feb 21, 2023 · 0 comments
Open

Segmentation fault when running Chrome with hextype #10

YizhuoZhai opened this issue Feb 21, 2023 · 0 comments

Comments

@YizhuoZhai
Copy link

Hi:
I have successfully built the Chrome with HexType's instrumentations, but I met two problems when running the instrumented Chrome:
1.
Program received signal SIGSEGV, Segmentation fault.
0x00005555560ea8b6 in __update_direct_oinfo ()

This happens in hextype.cc, function __update_direct_oinfo (), when checking if (ObjTypeMap[MapIndex].ObjAddr == nullptr), loading from the ObjTypeMap[MapIndex].ObjAddr causes the crash.
2.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff7120c20 in base::internal::OnNoMemoryInternal(unsigned long)

This happens in hextype.cc, in function __update_phantom_info () when allocate the ObjTypeMap:
ObjTypeMap = new ObjTypeMapEntry[NUMMAP];

Do you have any suggestions for solving those issues? I upgrade the hextype into llvm-14.0.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant