devu-uhci crashed on me, I got a core dump if you like
IP: 0x804e214
- Mario
Mario Charest <mcharest@nozinformatic.com> wrote:
devu-uhci crashed on me, I got a core dump if you like
IP: 0x804e214
Please send the dump file. BTW, what were you doing at the
time of the crash? What devices were connected?
On 30 Apr 2001 11:13:11 GMT, Kevin Chiles <kchiles@qnx.com> wrote:
Mario Charest <> mcharest@nozinformatic.com> > wrote:
devu-uhci crashed on me, I got a core dump if you likeIP: 0x804e214
Please send the dump file.
It’s in ~ on QUICS.
BTW, what were you doing at the
time of the crash? What devices were connected?
Unfortunately I don’t know. There is only one device connected a
custom printer. I wrote the class driver for it. I used the printer
class driver as a template, it underwent very little change. At
one point I had a bug in it where I opened two different IN endpoints
(the printer has 2 in and two out), using the same ep_in variable.
However I’m not sure if I had fix it before the core dump or nor.
The custom printer is somewhat limited, it can’t handle USB
communication while it’s printing. Plus the code in the printer is
still being debugged. There are lots of timeout error when dealing
with this printer.