Changes between Version 3 and Version 4 of Ticket #10186, comment 7


Ignore:
Timestamp:
Feb 20, 2014, 6:54:54 AM (5 years ago)
Author:
cypherpunks
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10186, comment 7

    v3 v4  
    11~~We could to create two version of backtrace for windows.
    22First, if build with MSVC (then no problem pdb files, and if user used MSVC they knows what to do with pdb files for all modules).
    3 Second, if build with mingw toolchains then it's possible to use idea of code from [https://code.google.com/p/backtrace-mingw/ backtrace-mingw]. It should to produce the same output as for backtrace()'s platforms~~. Just did read code, it's the same StackWalk, sad. I wonder how symbol part work.
    4 [https://code.google.com/p/backtrace-mingw/ backtrace-mingw] working with fresh binutils but showing symbols only if debug information wasn't striped. No -rdynamic supported either.
     3Second, if build with mingw toolchains then it's possible to use idea of code from [https://code.google.com/p/backtrace-mingw/ backtrace-mingw]. It should to produce the same output as for backtrace()'s platforms~~. ~~Just did read code, it's the same StackWalk, sad. I wonder how symbol part work.
     4[https://code.google.com/p/backtrace-mingw/ backtrace-mingw] working with fresh binutils but showing symbols only if debug information wasn't striped. No -rdynamic supported either.~~ Almost all stacktrace vanishes if FPO, no matter what symbols generated gcc.