Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. SetWindowLong indicates blocked thread.

SetWindowLong indicates blocked thread.

Scheduled Pinned Locked Moved C / C++ / MFC
questionhelpworkspace
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    suninwater
    wrote on last edited by
    #1

    SetWindowLong indicates blocked thread. Hi,guys: I got a problem and any response is much appreciated. :-) Environment: windows2000sp4,vc6sp5 92: LONG style = GetWindowLong(m_hwnd, GWL_STYLE); 93: style |= WS_DLGFRAME | WS_THICKFRAME; 94: SetWindowLong(m_hwnd, GWL_STYLE, style); 1000FD13 mov esi,esp 1000FD15 mov eax,dword ptr [ebp-8] 1000FD18 push eax 1000FD19 push 0F0h 1000FD1B mov ecx,dword ptr [ebp-4] 1000FD1E mov edx,dword ptr [ecx+194h] 1000FD24 push edx 1000FD25 call dword ptr [__imp__SetWindowLongA@12 (10090a28)] 1000FD2B cmp esi,esp 1000FD2D call __chkesp (1002cac0) Everything is ok till 1000FD25 call dword ptr [__imp__SetWindowLongA@12 (10090a28)] when single step debugging. The thread seems suspended at this line and never process any more. How can I solve this problem ? Thanks you very much !

    P 1 Reply Last reply
    0
    • S suninwater

      SetWindowLong indicates blocked thread. Hi,guys: I got a problem and any response is much appreciated. :-) Environment: windows2000sp4,vc6sp5 92: LONG style = GetWindowLong(m_hwnd, GWL_STYLE); 93: style |= WS_DLGFRAME | WS_THICKFRAME; 94: SetWindowLong(m_hwnd, GWL_STYLE, style); 1000FD13 mov esi,esp 1000FD15 mov eax,dword ptr [ebp-8] 1000FD18 push eax 1000FD19 push 0F0h 1000FD1B mov ecx,dword ptr [ebp-4] 1000FD1E mov edx,dword ptr [ecx+194h] 1000FD24 push edx 1000FD25 call dword ptr [__imp__SetWindowLongA@12 (10090a28)] 1000FD2B cmp esi,esp 1000FD2D call __chkesp (1002cac0) Everything is ok till 1000FD25 call dword ptr [__imp__SetWindowLongA@12 (10090a28)] when single step debugging. The thread seems suspended at this line and never process any more. How can I solve this problem ? Thanks you very much !

      P Offline
      P Offline
      Prakash Nadar
      wrote on last edited by
      #2

      I have used those lines of code before, i never had any problem with that, just make sure that the window handle is valide. The World is getting smaller and so are the people.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups