Bug 49341

Summary: system locks up when I quit my application from the xWindows enviroment, this doesn't happen in non-xwindows environment, Please contact me for the details.
Product: [Applications] kdevelop Reporter: Kenny Cheung <cheung>
Component: kdevelop 2.x (obsolete)Assignee: KDevelop-Devel List <kdevelop-devel>
Status: RESOLVED NOT A BUG    
Severity: crash    
Priority: NOR    
Version First Reported In: 2.0   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Kenny Cheung 2002-10-18 15:50:29 UTC 
Version:           2.0 (using KDE KDE 1.2)
Installed from:    RedHat RPMs
Compiler:          gcc 
OS:          LinuxLinux

I am developing software package (driver, library, and applications) for a pcmcia communication card. The software is interrupt driven. My library is blocked and it waits for the driver to pass back an interrupt message so it could go out and pull the data in from the card or send data out. This is whole process works great in a non-xwindow environment. The problem is that it just doesn't work under Kdevelop 2.0 with the xwindow running. I am constanting missing data or data is jammed into my software queue. And if I quit the application while the process is running, the whole system locks up. It sounds like an interrupt problem, but it turned out to be not, because if I ran my console application in the non-xwindow environment, I could see that the interrupt was freed even if I quitted in the middle of the process. And the system didn't lock up. I'll really appreciate that if you could tell me if there was anything similar to this reported by other developers. Or if you know what the possible problem is. Please let me know if you need more detail.
Comment 1 Caleb Tennis 2003-01-01 01:36:50 UTC 
This isn't so much a KDevelop problem as a thread/event problem.  You need to 
investigate what with XWindows is causing the problem.