Re: Kill a thread - C / C++ / MFC Discussion Boards

Re: Kill a thread

bouli1-Apr-05 2:43

bouli

1-Apr-05 2:43

I wish the creator of the thread kill his created thread:

while (!m_dwBytesRead && (nRetries < 2600))<br />
{<br />
m_pReadThread=AfxBeginThread(ReadThread, this, THREAD_PRIORITY_NORMAL);<br />
<br />
nRetries++;<br />
::Sleep(600);<br />
<br />
if (!m_dwBytesRead)<br />
{<br />
// Kill the thread m_pReadThread<br />
}<br />
}

There is no spoon.

Re: Kill a thread

toxcct1-Apr-05 2:49

toxcct

1-Apr-05 2:49

ok, i so repost my question :

don't SendMessge() work with the correct argument ? (i don't remember which, but it might be something like WM_KILL or WM_END)... of course, sent to the correct thread, ie. m_pReadThread

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Re: Kill a thread

bouli1-Apr-05 3:10

bouli

1-Apr-05 3:10

no, the owner of the thread is not a window. the owner of the thread is a CObject derived class. There must be a way for the owner of the thread to kill its own created thread without condition.

There is no spoon.

Re: Kill a thread

toxcct1-Apr-05 3:19

toxcct

1-Apr-05 3:19

where did you see that SendMessage() was a member of CWindow or CDialog or i don't even know what else... there's a global one ...

but if you don't want (and you ahve the right to), don't do it ...

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Re: Kill a thread

bouli1-Apr-05 3:25

bouli

1-Apr-05 3:25

Hi,

I have explained the purpose of the thread a little bit late. So I repeat the purpose:

the thread just call the ReadFile API. So, if nothing comes, the ReadFile API waits indefinitly. Thus, I can't use OVERLAPPED because it is not supported by the driver. So, I can use only synchronous IOs in my thread. The way I want to handle the ReadFile timeouts (it's not serial IOs) is to use the ReadFile API in a thread and the caller create and destroy the thread after an amount of time while nothing comes. If something comes, the thread finish itself naturally.

I can create the thread, but I don't know how I can destroy the thread FROM the caller. not inside the thread itself.

so, you understand, that if I try to exit FROM the created thread, once it waits for data from the ReadFile, I can wait forever and the thread never exits because it is blocked by the ReadFile API. That's why I need to kill the thread from outside without condition. see what I mean?

thanks.

There is no spoon.

Re: Kill a thread

ThatsAlok1-Apr-05 18:35

ThatsAlok

1-Apr-05 18:35

Hain Tox!!!
Actually Worker thread don't have any message handlling capability! So how it's going to handle SendMessage(...) Thread.

Same thing is possible with UI threads where you can use PostThreadMessage(..)to send message to the thread!

[Vote One Here, Complete my Survey....]

Alok Gupta
visit me at http://www.thisisalok.tk

"I ~~Think~~ Believe this Will Help"

Re: Kill a thread

eli150219791-Apr-05 3:10

eli15021979

1-Apr-05 3:10

why can't you use global flag and in your child thrad put the code in a loop,like this(Exit is boolian veriable from CTestDlg class):

void CTestDlg::OnTest()
{
    while (!m_dwBytesRead && (nRetries < 2600))
    {
          Exit = false;
          m_pReadThread=AfxBeginThread(ReadThread, this,  THREAD_PRIORITY_NORMAL);

          nRetries++;
          ::Sleep(600);

          if (!m_dwBytesRead)
          {
               Exit = true;// Kill the thread m_pReadThread
          }
    }    
}

UINT ChildThrad(LPVOID lpvoid)
{
    CTestDlg *dlg = (CTestDlg *)lpvoid;
    while(!dlg->Exit)
    {
       //put your child thread code here
    }
    return 0;
}

Re: Kill a thread

bouli1-Apr-05 3:17

bouli

1-Apr-05 3:17

the thread just call the ReadFile API. So, if nothing comes, the ReadFile API waits indefinitly. Thus, I can't use OVERLAPPED because it is not supported by the driver. So, I can use only synchronous IOs in my thread. The way I want to handle the ReadFile timeouts (it's not serial IOs) is to use the ReadFile API in a thread and the caller create and destroy the thread after an amount of time while nothing comes. If something comes, the thread finish itself naturally.

I can create the thread, but I don't know how I can destroy the thread FROM the caller. not inside the thread itself.

Best regards.

There is no spoon.

Re: Kill a thread

BadJerry1-Apr-05 3:47

BadJerry

1-Apr-05 3:47

If you want to kill off a thread, you could mention how to do it in VB .... oops sorry I am still in April Fools day mood!
Seriously, you can call (but never advised because of its sheer brutality)
::TerminateThread(m_hThread,0);

Re: Kill a thread

bouli1-Apr-05 3:50

bouli

1-Apr-05 3:50

I just wanted that Smile | :)

at last, you understood my needs Smile | :)

and now, I have memory leaks, Laugh | :laugh:

There is no spoon.

Re: Kill a thread

Blake Miller1-Apr-05 4:55

Blake Miller

1-Apr-05 4:55

Memory leaks because you called TerminateThread(), who would have thought.... Just kidding.
But of COURSE you have memory leaks, since your thread did not terminate 'normally'.

You really ARE dealing with a poorly designed driver, aren't you? They should have provided at least a 'is data available' call for you or something. Is there truly no way to set any kind of timeout in case there is no data? Most device drivers will just return that there are no bytes to read instead of hanging your thread up.

Part of your leak might be from the CWinThread object returned from the AfxBeginThread call. When you assssinate your thread, you might want to at least delete the CWinThread object data.

I truly encourage you to seek another driver, or at least a design option that does not force you to continually start and kill threads in this manner.

Good luck!

Re: Kill a thread

bouli1-Apr-05 5:05

bouli

1-Apr-05 5:05

Hi,

When I delete the thread from the m_pThread (CWinThread*) it crashes. So, I am using the simple Win32 API function CreateThread and TerminateThread and there is no memory leaks. Laugh | :laugh:

Why doing complex as we can do simple?

Indeed, the driver is poorly implemented. It's a USB driver for HP calculators (shipped by HP) and it does not handle correctly the overlapped IO (the system crashes when I use overlapped IOs), if it would have handle them correctly, of course, overlapped IO would have been much more simple. But now, with this brutal algorithm of calling ReadFile in a thread and kill the thread after an amount of time and repeat the operation until something comes works fine now Smile | :)

But I'm agree that overlapped IO should be the best choice. Of course, using overlapped IOs, is the first idea that came in mind. Wink | ;)

There is no spoon.

Re: Kill a thread

bouli1-Apr-05 5:05

bouli

1-Apr-05 5:05

But I'm agree that overlapped IO should be the best choice. Of course, using overlapped IOs, is the first idea that came in mind. Wink | ;)

Thanks to all of you for the help Smile | :)

Best regards.

There is no spoon.

Re: Kill a thread

David Crow1-Apr-05 3:56

David Crow

1-Apr-05 3:56

See here.

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

Dialog resource

The Professor1-Apr-05 2:08

The Professor

1-Apr-05 2:08

Hi
I am trying to add a dialog to an existing project.

I add the resource file .rc then add the dialog and double click on it an the class creator/wizard thing appears so I enter the class name.

Now I try to add a button and test it by adding a show message to it's event handler.

The problem is, it doesn't compile and the error is:
IDD_DIALOG1 = undefined

enum {IDD = IDD_DIALOG1};

Help!

Re: Dialog resource

toxcct1-Apr-05 2:15

toxcct

1-Apr-05 2:15

why did you copy the .RC file ???

as far as i know, when you create a dialog, you set its ID. the same when you add a button to the dialog... then, you can associate an event handler to that ID...

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Re: Dialog resource

The Professor1-Apr-05 12:13

The Professor

1-Apr-05 12:13

toxcct wrote:
why did you copy the .RC file ???

I created the .rc file i.e. added it to the project
then the dialog is added as a child of the .rc file

Am I doing this all wrong?

Can you step me through what you would do to add a dialog with a button?

Cheers

Re: Dialog resource

ThatsAlok1-Apr-05 2:17

ThatsAlok

1-Apr-05 2:17

Just above class Decalaration add #include"resource.h" and then rebuild your project

[Vote One Here, Complete my Survey....]

Alok Gupta
visit me at http://www.thisisalok.tk

"I ~~Think~~ Believe this Will Help"

Re: Dialog resource

David Crow1-Apr-05 3:58

David Crow

1-Apr-05 3:58

TheProffessor wrote:
I am trying to add a dialog to an existing project.

Exactly how did you do this?

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

Re: Dialog resource

The Professor1-Apr-05 12:20

The Professor

1-Apr-05 12:20

#include"resource.h" didn't work
still get the same error
error C2065: 'IDD_SHUTDOWN' : undeclared identifier

Re: Dialog resource

ThatsAlok1-Apr-05 18:05

ThatsAlok

1-Apr-05 18:05

Then Check wheather IDD_SHUTDOWN is defined in Resource.h or not!

[Vote One Here, Complete my Survey....]

Alok Gupta
visit me at http://www.thisisalok.tk

"I ~~Think~~ Believe this Will Help"

Re: Dialog resource

The Professor2-Apr-05 18:43

The Professor

2-Apr-05 18:43

ThatsAlok wrote:
Then Check wheather IDD_SHUTDOWN is defined in Resource.h or not!

It wasn't defined! But now I get lots of errors saying that everything is already defined in a .obj file.
????

About Windows Explorer-style TreeView

Kim Myong1-Apr-05 1:54

Kim Myong

1-Apr-05 1:54

Hi,
How can implement Windows Explorer-style folder tree view?
Would any one give me a hint?

Regards.

Re: About Windows Explorer-style TreeView

Alexander ^M.,1-Apr-05 2:54

Alexander ^M.,

1-Apr-05 2:54

http://www.codeproject.com/treectrl/shelltreectrl.asp[^]

Don't try it, just do it! Wink | ;-)

Re: About Windows Explorer-style TreeView

Kim Myong1-Apr-05 3:41

Kim Myong

1-Apr-05 3:41

Thank you!

And would you let me know how can implement Explorer-style file list view?

Regards.

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.