Open GoogleCodeExporter opened 9 years ago
I did finally get a copy of the source and saw this behavior was because
Map2Dbg always wants to flag the target binary as having debug info stripped.
While I understand why that might be desirable under some circumstances, I'd
like to request a change where a command-line option would be added to
optionally NOT alter the executable. That would meet our needs and also allow
other uses to flag the .EXE as was done before.
Original comment by riddle...@gmail.com
on 2 Apr 2014 at 7:16
Of course, everything is possible :)
But why not including a version number or hash in the exe itself? (custom
verion info).
You can easily fetch it by using TJclPeImage.VersionInfo.Items.
That's the way we do it with our version control system (Plastic SCM) by
including the changeset number + branch name in the exe, so we know exact which
source code is used.
The same can you do with a hash or whatever. But you need for example an
automated build server for that like FinalBuilder.
We also include JDBG in the exe to be 100% sure we have the right debug
symbols. In the JCL there is a tool to compile/compress a big .map file to a
.jdbg and add it as a JCLDEBUG section in the .exe.
I also made 2 tools that can be used for this:
- the live stack viewer in my Sampling Profiler
https://code.google.com/p/asmprofiler/wiki/ProcessStackViewer
- offline minidump reader (!)
https://asmprofiler.googlecode.com/svn/trunk/MiniDumpReader/ViewMinidump.exe
These 2 tools both can use the internal jdbg (or other debug symbols) and you
have full debug info (e.g. line numbers) which you don't have with map2dbg
Original comment by andre.mussche
on 2 Apr 2014 at 7:43
Original issue reported on code.google.com by
riddle...@gmail.com
on 2 Apr 2014 at 3:00