overriden 'int' module lacks functionality of the original one
The int module that we defined in order to go around a hardcoded value in the debugger should provide all the functionality of the original one.
Since the integrated debugger doesn't provide everything we need yet, one needs sometimes go to the console and run the command from there (for example, to interpret a module that isn't in the project path).
We should be careful so that it works at least with R12 and R13, hopefully even with R11
Since the integrated debugger doesn't provide everything we need yet, one needs sometimes go to the console and run the command from there (for example, to interpret a module that isn't in the project path).
We should be careful so that it works at least with R12 and R13, hopefully even with R11
Leave a comment
on 2009-07-16 11:47 *
By jakobc
Assigned to set to jakobc
Status changed from New to Accepted
Assigned to set to jakobc
Status changed from New to Accepted
There is a module 'erlide_int' which is basically the same as 'int'. I can provide bridge from int to erlide_int. What functionality is needed?
The reason that 'int' is overridden is that the int module is hard-coded in the beam emulator as the module to call on emulator breakpoints. This should change sometime in the future, but it's not highly prioritized in OTP.
The reason that 'int' is overridden is that the int module is hard-coded in the beam emulator as the module to call on emulator breakpoints. This should change sometime in the future, but it's not highly prioritized in OTP.
on 2009-07-16 12:09 *
By Vlad Dumitrescu
Ah, I didn't see erlide_int, it's probably good enough to use that one instead. There is still a question mark about if the version we have will work with R13 (or if it's copied from there, with R12).
The requirement triggering this was to the ability to interpret modules from the standard libraries and set breakpoints in them.
The requirement triggering this was to the ability to interpret modules from the standard libraries and set breakpoints in them.
on 2009-07-16 12:56 *
By Vlad Dumitrescu
there is an alternative way to tweak the int module: hack the beam code when loading it, so that we override int:eval/3 with our own version. This would take care of the R12/R13 issue, the only disadvantage is that you can't debug the int module from erlide (but who would want that, anyway? :-)
on 2009-07-16 13:42 *
By Vlad Dumitrescu
Ok, but then we have to make sure it works with R11, R12 and R13. For example, there is some scanner related stuff, where in R13 we have a new format for tokens.