Bug 1482419 - PDB symbol files are missing for some virtio-win binaries
Summary: PDB symbol files are missing for some virtio-win binaries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Danilo de Paula
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1457845
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-17 08:43 UTC by lijin
Modified: 2018-04-10 06:33 UTC (History)
5 users (show)

Fixed In Version: virtio-win-1.9.4-1.el7.src.rpm
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1457845
Environment:
Last Closed: 2018-04-10 06:31:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0657 0 None None None 2018-04-10 06:32:59 UTC

Comment 1 Jeff Nelson 2017-08-18 17:25:27 UTC
Description of problem:
A subset of virtio-win binaries doesn't have their symbol files persisted anywhere. Not even in the raw prewhql build. They are lost forever after a build is completed and the build machine recycled.


--- Additional comment from Ladi Prosek on 2017-07-14 02:12:44 EDT ---

Fixed in commits:

https://github.com/virtio-win/kvm-guest-drivers-windows/commit/c9a3abccc854a8e1c7223b3ee6d1ebff0a6940cc
https://github.com/virtio-win/kvm-guest-drivers-windows/commit/9286da9e4a98712ca64aa3040ee204f8caf9ad92

I'll update virtio-win packaging scripts once a raw build with these fixes is available.


--- Additional comment from lijin on 2017-08-17 04:41:03 EDT ---

[...]

I will clone this bug to distribution sub-component as it affects virtio-win packaging as well

Comment 5 lijin 2018-01-18 01:57:47 UTC
Check in virtio-win-1.9.4-1.el7.noarch, these pdb files are not existing, so change status to verified.

Thanks

Comment 7 errata-xmlrpc 2018-04-10 06:31:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0657


Note You need to log in before you can comment on or make changes to this bug.