-
Notifications
You must be signed in to change notification settings - Fork 1
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
gdb error in terminal when debugging translators #97
Comments
A relevant web link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867314 |
@ouankou Can we have a docker image with debug build of ROSE? |
OK, I created a specific docker image for previous loop stride bug. I'll create a similar one for debug build of ROSE and address this issue. |
Follow the building instruction from: https://en.wikibooks.org/wiki/ROSE_Compiler_Framework/How-tos#How_to_debug_a_translator Address the following issue: chunhualiao/freeCompilerCamp#97
@chunhualiao I've uploaded a new docker image of ROSE debug build. freeCompilerCamp/play-with-compiler@96bf3fa docker pull freecompilercamp/pwc:rose-debug A related tutorial has been set to use this specific image as example. http://freecompilercamp.org/rose-ast-traversal/ About this issue, I tried several different configurations of JDK and OS. It seems like an upstream bug of JDK8 debug extension of GDB. When GDB loads the JDK 8 debugger plugin
If I switch to OpenJDK 11, debugging the same JAR file is fine. It's not an issue of ROSE. Any program that involves JDK 8 will trigger this bug in GDB. I used the same method from this link to test, however, its solution doesn't work. This page has a long discussion about this issue. In their case, OpenJDK 9 works while OpenJDK 8 has the same issue as ours. I think the possible solutions could be:
Solution 1 is just a workaround. Solution 3 may be better in the long term. ROSE will eventually use some more recent version of OpenJDK anyway. Later I'll check whether Oracle JDK 8 has the same issue or not. |
freecc@node1:rose-ast$ gdb dotGenerator -c func1.c
The text was updated successfully, but these errors were encountered: