mfeoli
08-Dec-2005, 09:50 PM
This is the situation:
My application was built to receive many calls from a hardware interfase.
We built a component which handles the interfase, the component has a thread which loops looking for events on the hardware and then executes procedures on the main thread of the component which fires the events of the actual component.
On the main application the events of the component are received and handled on a single thread (multitasking) so many instructions are executed (all asynchronously) each time.
The problem is when heavy trafic of events comes on the board and on the component , for some unknown reason the application closes down without a message.
BUT EurekaLOG does not writes the error to the elf file, and it is working because on other errors (ussually on the main thread) it works fine and writes the information to the .elf file and all.
Any ideas of what may be wrong?
My application was built to receive many calls from a hardware interfase.
We built a component which handles the interfase, the component has a thread which loops looking for events on the hardware and then executes procedures on the main thread of the component which fires the events of the actual component.
On the main application the events of the component are received and handled on a single thread (multitasking) so many instructions are executed (all asynchronously) each time.
The problem is when heavy trafic of events comes on the board and on the component , for some unknown reason the application closes down without a message.
BUT EurekaLOG does not writes the error to the elf file, and it is working because on other errors (ussually on the main thread) it works fine and writes the information to the .elf file and all.
Any ideas of what may be wrong?