I guess it could be something with resources that run out, or perhaps a buffer overflow that writes some instructions in memory it shouldn't write in which causes wrong instructions to be executed (you could imagine that if a program is writing data in the wrong place of memory where at that moment is a proces that is being executed ( worse case the kernel ), it's going to contain wrong instructions, which are going to be executed).
I got no idea how go can check these thing, I know about libsafe, a library that sends a SIGKILL to a proces when a buffer overflow occurs ( I made a debian package, you can get it at: ftp://rademaker.dhs.org in pub/linux/debian/packages/binary-i386/ ). However, this buffer overflow is only something that I think could be it, I'm not saying it is the problem! Ron Rademaker On Mon, 19 Jun 2000, erasmo perez wrote: > hello everybody > > hi guys! long time not seeing you > > i have a small problem, that turned out to be important > > i have a notebook travelmate 5300 (texas inst.) which works > fine under linux, it has a sounblaster sound card, i guess that > integrated to the mainboard > > the problem that interest me now is the reception of sound using > speakfreely > > this machine can reproduce sound, can record sound, can play mp3 > files, can record using sound-recorder, and can send sound using > speakfreely, and in fact, it can also receive sound using speakfreely (sf) > > the problem is that when it is reproducing sound using sf, after some > moments of paceful reproduction of sound, the machine hangs, stops and > i need tu turn off the power button, as in an interruption request > problem > > but when i check /proc/interrupts there is no interruption collision, > and, by the way, i could install the module of sound without interrupt > collision problems > > so, it is interesting because this problem only arises after some > seconds of paceful reproduction, since it starts playing the sound of > sf, *last* some seconds and after that the machines hangs :-( > > which could be the reason for this problem, and how could i overcome > this situation ? > > thanks a lot > > erasmo > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
