[Bug 30973] New: Unsupported symbol id warnings when backtracing with Visual C 2010 .pdb files

http://bugs.winehq.org/show_bug.cgi?id=30973

Bug #: 30973
           Summary: Unsupported symbol id warnings when backtracing with
                    Visual C 2010 .pdb files
           Product: Wine
           Version: 1.5.6
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: dbghelp
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

I built the tiny demo from bug 835 with Visual C 2010, and ran it under Wine.
Happily, Wine generated good backtraces still,
but there were several unsupported symbol id warnings, e.g.

fixme:dbghelp_msc:codeview_snarf Unsupported symbol id 113e
fixme:dbghelp_msc:dump 00000000: 1a 00 3e 11 08 10 00 00 01 00 45 78 63 65 70
74  ..>.......Except
fixme:dbghelp_msc:dump 00000010: 69 6f 6e 52 65 63 6f 72 64 00 00 00           
  ionRecord...    
fixme:dbghelp_msc:codeview_snarf Unsupported symbol id 1141
fixme:dbghelp_msc:dump 00000000: 0e 00 41 11 11 00 00 00 dc 16 00 00 01 00 27
00  ..A...........'.
fixme:dbghelp_msc:codeview_snarf Unsupported symbol id 1144
fixme:dbghelp_msc:dump 00000000: 06 00 44 11 08 00 00 00                       
  ..D.....

There are so many of these warnings that it's easy to miss the fact
that there's still a good stack trace.
See the full log at
http://kegel.com/wine/valgrind/pdbdemo2/crash-vc2010-Zi/wine.log

The compiled app and pdb file are in
http://kegel.com/wine/valgrind/pdbdemo2.tgz

[Bug 30973] Unsupported symbol id warnings when backtracing with Visual C 2010 .pdb files

https://bugs.winehq.org/show_bug.cgi?id=30973

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download, source, testcase

--- Comment #1 from Austin English  ---
Still in wine-1.7.19-70-gd6a59f7.

[Bug 30973] Unsupported symbol id warnings when backtracing with Visual C 2010 .pdb files

https://bugs.winehq.org/show_bug.cgi?id=30973

--- Comment #2 from Austin English  ---
Created attachment 48701
  --> https://bugs.winehq.org/attachment.cgi?id=48701
terminal output/backtrace

[Bug 30973] Unsupported symbol id warnings when backtracing with Visual C 2010 .pdb files

https://bugs.winehq.org/show_bug.cgi?id=30973

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Austin English  ---
*** Bug 36885 has been marked as a duplicate of this bug. ***

[Bug 30973] Unsupported symbol id warnings when backtracing with Visual C 2010 .pdb files

https://bugs.winehq.org/show_bug.cgi?id=30973

--- Comment #4 from Austin English  ---
Created attachment 48978
  --> https://bugs.winehq.org/attachment.cgi?id=48978
patch to ignore more symbols

This avoids the spam.

[Bug 30973] Unsupported symbol id warnings when backtracing with Visual C 2010 .pdb files

https://bugs.winehq.org/show_bug.cgi?id=30973

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
      Fixed by SHA1|                            |8980a6fa5c1128650d478739deb
                   |                            |ef10f56bcd300
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Austin English  ---
Fixed by
https://source.winehq.org/git/wine.git/commitdiff/8980a6fa5c1128650d478739de...

[Bug 30973] Unsupported symbol id warnings when backtracing with Visual C 2010 .pdb files

https://bugs.winehq.org/show_bug.cgi?id=30973

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #6 from Alexandre Julliard  ---
Closing bugs fixed in 1.7.23.