Is this normal?

[Lost User]

With threads this is quite possible. If you are doing work like this get your manager to OK buying a couple of decent books.

Join the cool kids - Come fold with us[^]

[Mark_Wallace]

There's a verrrry good article Here[^]. It might take a bit to wade through it, if you're unfamiliar with the language/syntax, but the logic and usage are impeccable.

I wanna be a eunuchs developer! Pass me a bread knife!

[Joe Woodbury]

Odds are you have runaway threads, which cause a system to appear locked up.

[Richard Jones]

Christian Graus wrote:

Who do you work for ?

I realize this is old, but I was hoping he would say "Telstra" :laugh:

"The activity of 'debugging', or removing bugs from a program, ends when people get tired of doing it, not when the bugs are removed." - "Datamation", January 15, 1984

[PaulowniaK]

Norm .net wrote:

Oh dear Sigh Threads and the unexperienced are a recipe for disaster.

That's... very comforting to know... ... ... X|

[PaulowniaK]

Joe Woodbury wrote:

Odds are you have runaway threads, which cause a system to appear locked up.

Most likely...:thumbsup:

[PaulowniaK]

Thanks for the info.:thumbsup: It's quite hard, but I'll try reading it.

[NormDroid]

You know, you wouldn't do open heart surgery without training and experience, the same goes with software engineering.

All right, you guys, I got eight crates of Ipecac from Mort. All on my tab. Now, whoever goes the longest without puking gets the last piece of pie in the fridge.

[PaulowniaK]

Norm .net wrote:

You know, you wouldn't do open heart surgery without training and experience

True... but it's not so common that you kill someone by writing bad code... I'm sure you can (f-ing up the software used in air traffic control, say) but in my case, the worst that is going to happen is that some ionized molecules are going to go to ionized molecule heaven.

[Corinna John]

There are two usual causes to freezing machines: 1) Memory leaks: Watch your memory usage in Task Manager. Does it rise faster than you can explain? Then you very likely forgot to free the memory of some objects which you create in a loop. 2) Never ending loops: Watch you CPU time in Task Manager. Does it reach 100% before the machine freezes? Then very likely a break condition is never reached (i.e. you loop over a list, but forget to increment the index). As you are unexperienced, only a debugger can save you.

This statement is false.

[IncredibleMouse]

That was a brilliant response to the inaccurate comparison. :thumbsup:

[IncredibleMouse]

You will never learn, unless you try. Succeed or fail, don't give up. Assuming of course you actually like what you're doing/learning. Never listen to another's notion that you "can't" or "shouldn't". Yes, malformed threads can cause the behavior you are experiencing, and they will extend to the end-user unless corrected.

[Jason Christian]

If you're not a programmer you might want to convince someone to let you program in something other (i.e. easier, or more forgiving) than C++.

[Jay Elston]

Actually, you _can_ kill people with bad code. You should subscribe to comp.risks. It is replete with stories about how software causes death or destruction.

[fglenn]

I am reminded of a quote that I read many years ago, and I cannot remember who said it: "'C' will allow you to shoot yourself in the foot. 'C++' makes it harder, but if you succeed, it will take off your whole leg." :laugh:

Fletcher Glenn

[patbob]

It can. Depends a lot on what you're doing and in which functions. The machines that windows runs on have gotten a lot better over time, but the old Win32 GUI thread bug is still there -- it stops by my PC for a scotch and to reminisce every now and then. I don't usually have to reboot to exorcise it anymore like the old days -- logging out and back in is usally as bad as things get, and rarely that anymore. Just part of the (un)fun of programming sometimes. Now if the mosue stops working, that's a differnet matter.

patbob

[Yortw]

"Not a Programmer" + "C++" + "Threads" = BOOM ! :-D Yes, that would be expected, at least to some degree. It's a little suprising the whole machine locked up rather than just your app, but you are working in C++ where you can shoot yourself in the foot in many different ways so it is possible to lock up the entire PC (deadlocking the kernel somehow, for instance). Good luck, you're going to need it :) http://burks.bton.ac.uk/burks/language/shoot.htm[^]

[Lost User]

Yeah dats much normal, i dont even write much code just solved issues these days

Ravie Busie Coding is my birth-right and bugs are part of feature my code has! _________________________________________ Me  Facebook  Twitter

[Jinjav]

Write and test your code in a virtual machine.... You will just have to reboot the virtual machine if it crashes. I used to do that when programming the Linux Kernel... It will then make the task so much easier and won't affect your hardware :)

[User 4566656]

Hi, I have a suspicion about your problem: The DLL you've mentioned: does it in any way communicate with a device? What you said about those ionized molecules supports this. When there's a hardware driver that has been written for internal use, and a DLL that provides an API for it, also meant for internal use, chances are high that these are not as robust as drivers and DLLs meant for the consumer market. That means that it is often easy to write code using such an API or driver that crashes the operating system's kernel (that's the very core of the operating system). It does not mean that the driver and DLL are actually badly designed or written. It only means that they're not supposed to be used by a great number of developers out-of-house. My first guess for a solution: check what you've been writing against the documentation / source code / comments, whatever you have. Second guess: you've actually broken your own code via some flaw in your use of threads that leads to some kind of unexpected behavior that, via the DLL and the driver, crashes the kernel. So, unless the first approach was sufficient, find out whether the behavior you've encountered is reproducible without multiple threads. Cheers from Vienna, The Continent