http://bugs.winehq.org/show_bug.cgi?id=2096
------- Additional Comments From carl.sopchak@cegis123.com 2004-22-04 15:16 ------- Well, I tried to produce a trace, but wine doesn't crash when run with --debugmsg +relay. It does, however, put these fixme's in the log:
fixme:bitmap:CreateCompatibleBitmap got bad width 0 or height 1075782048, please look for reason fixme:bitmap:CreateCompatibleBitmap got bad width 0 or height 1075782048, please look for reason fixme:bitmap:CreateCompatibleBitmap got bad width 0 or height 1075782048, please look for reason fixme:bitmap:CreateCompatibleBitmap got bad width 0 or height 1075782048, please look for reason
When run without --debugmsg +relay, wine does crash, and the fixme's generated are:
fixme:bitmap:CreateCompatibleBitmap got bad width 1076953140 or height 64, please look for reason fixme:bitmap:CreateCompatibleBitmap got bad width 1076953140 or height 64, please look for reason fixme:bitmap:CreateCompatibleBitmap got bad width 1082579840 or height 1075569213, please look for reason fixme:bitmap:CreateCompatibleBitmap got bad width 1082579840 or height 1075569213, please look for reason
Since the values shown for the height/width of the bitmap are different when running the EXACT same scenario, it further leads me down the road toward a bad parameter pass...
What should be my next step? I could try playing with the gdi32.spec file, but I REALLY have *NO* idea what I'm doing there... (I could try just replacing the apparently erroneous "long"s with "int"s, leaving everything else alone, I guess...)
Carl