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

timeout in erlide_debug:interpret/4 #310

Open
georg-w-mueller opened this issue Oct 27, 2017 · 3 comments
Open

timeout in erlide_debug:interpret/4 #310

georg-w-mueller opened this issue Oct 27, 2017 · 3 comments
Assignees

Comments

@georg-w-mueller
Copy link

Ladies, Gents, Contributors,

Just for information: Debugging fails, no halt at breakpoints, no process information
More details -> Logfile attached

Configuration:
Erlang/OTP 20 [erts-9.1] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:10]
Eclipse IDE for Java Developers Version: Oxygen.1a Release (4.7.1a) Build id: 20171005-1200
eclipse.vm=C:\Program Files\Java\jre1.8.0_92\bin\server\jvm.dll
java.version=1.8.0_92, java.vm.info=mixed mode, java.vm.name=Java HotSpot(TM) 64-Bit Server VM
Erlide v0.52.2.201707181448~0.50.1.201707181420 (model api=0.50.1.201704202112) (kernel=?~0.115.1.201707181335)
Windows 10, 64bit, firewall deactivated
erlide.log

@vladdu
Copy link
Collaborator

vladdu commented Oct 27, 2017

Thanks, I will look at it.

@vladdu
Copy link
Collaborator

vladdu commented Jun 4, 2018

Sorry for the delay, I was working on a different project. Found the issue. hopefully I can fix and publish it soon.

@vladdu
Copy link
Collaborator

vladdu commented Jun 6, 2018

Notes to self (maybe write one ticket for each?):

  • The debugger code for v19 and v20 is wrong, calls removed module sys_pre_expand; probably modified while applying the erlide-specific patches, and never tested properly
  • Split the debuggers into separate plugins, and not rebuild/publish them every time. This will probably make the process of building and publishing easier (no need to always have installed all supported versions of Erlang).
  • Add debugger for v21
  • Review the erlide patches: can we make their application more secure? Document the procedure.
  • There are many parts of the kernel that aren't automatically tested, think if it's possible to do that. Simple smokescreen tests would be good too.

@jesperes I know you are interested in the debugger, you might want to keep an eye on this ticket and comment.

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

No branches or pull requests

2 participants