DynamoRIO / DynamoRIO/drmemory
Possible false pos uninit reported in user32.dll!GetClassLongW
- Dominant language
- C
- Stars
- 2.7k
- Forks
- 290
- PR merge metrics
- No merged PRs in 30d
Description
_From [rnk@google.com](https://code.google.com/u/rnk@google.com/) on February 29, 2012 14:33:12_
Example report:
[ RUN ] PrintPreviewHandlerTest.StickyMarginsCustom
~~Dr.M~~
~~Dr.M~~ Error `#1`: UNINITIALIZED READ: reading register edx
~~Dr.M~~ # 0 USER32.dll!GetClassLongW +0x25f (0x75778607 )
~~Dr.M~~ # 1 ntdll.dll!KiUserCallbackDispatcher +0x2d (0x77d8010a )
~~Dr.M~~ # 2 ui::CenterAndSizeWindow [ui\base\win\hwnd_util.cc:155]
~~Dr.M~~ # 3 views::NativeWidgetWin::CenterWindow [ui\views\widget\native_widget_win.cc:668]
~~Dr.M~~ # 4 views::Widget::SetInitialBounds [ui\views\widget\widget.cc:1218]
~~Dr.M~~ # 5 views::Widget::Init [ui\views\widget\widget.cc:341]
~~Dr.M~~ # 6 ConstrainedWindowViews::ConstrainedWindowViews [chrome\browser\ui\views\constrained_window_views.cc:567]
~~Dr.M~~ # 7 ConstrainedHtmlUI::CreateConstrainedHtmlDialog [chrome\browser\ui\views\constrained_html_delegate_views.cc:150]
~~Dr.M~~ # 8 printing::PrintPreviewTabController::CreatePrintPreviewTab [chrome\browser\printing\print_preview_tab_controller.cc:438]
~~Dr.M~~ # 9 printing::PrintPreviewTabController::GetOrCreatePreviewTab [chrome\browser\printing\print_preview_tab_controller.cc:228]
~~Dr.M~~ `#10` PrintPreviewHandlerTest::OpenPrintPreviewTab [chrome\browser\ui\webui\print_preview\print_preview_handler_unittes:70]
~~Dr.M~~ `#11` PrintPreviewHandlerTest::SetUp [chrome\browser\ui\webui\print_preview\print_preview_handler_unittes:50]
~~Dr.M~~ `#12` testing::internal::HandleExceptionsInMethodIfSupportedtesting::Test,void [testing\gtest\src\gtest.cc:2145]
~~Dr.M~~ Note: @0:10:52.575 in thread 3800
~~Dr.M~~ Note: instruction: test %edx %edx
[ OK ] PrintPreviewHandlerTest.StickyMarginsCustom (3562 ms)
It's a little confusing because line 155 of hwnd_util.cc is a call to AdjustWindowToFit defined above. I'm not familiar with Windows user callbacks so I don't know how they affect the stack trace. Not sure which win32 call is reaching this.
_Original issue: http://code.google.com/p/drmemory/issues/detail?id=810_
Contributor guide
Assessment
This issue has not been assessed yet.