You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 5505 Reporter: cgillot Assigned to:@protz Status: closed (set by @xavierleroy on 2013-08-31T10:46:31Z) Resolution: fixed Priority: low Severity: feature Category: back end (clambda to assembly) Duplicate of:#5487
Bug description
I've a c++ project using caml as extension language, calling (native) ocaml code via callbacks.
I would like to be able to debug both c++ and ocaml code in gdb, since the coupling between the languages is quite high.
Up to now, I've changed some asmcomp files in order to emit amd64 line informations.
The only meaningful code is in asmcomp/amd64/emit.mlp (the real symbols emission), and in bytecomp/translcore.ml (decorating lazy constructs).
The rest is transporting the information from one place to another.
Is it possible to have a more portable (and less hackish) version ?
Original bug ID: 5505
Reporter: cgillot
Assigned to: @protz
Status: closed (set by @xavierleroy on 2013-08-31T10:46:31Z)
Resolution: fixed
Priority: low
Severity: feature
Category: back end (clambda to assembly)
Duplicate of: #5487
Bug description
I've a c++ project using caml as extension language, calling (native) ocaml code via callbacks.
I would like to be able to debug both c++ and ocaml code in gdb, since the coupling between the languages is quite high.
Up to now, I've changed some asmcomp files in order to emit amd64 line informations.
Code based on the one found at :
http://blog.techno-barje.fr/post/2008/11/09/Ocaml-native-code-debugging/
The only meaningful code is in asmcomp/amd64/emit.mlp (the real symbols emission), and in bytecomp/translcore.ml (decorating lazy constructs).
The rest is transporting the information from one place to another.
Is it possible to have a more portable (and less hackish) version ?
File attachments
The text was updated successfully, but these errors were encountered: