[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CFRunLoopRun() hangs up after ReadPipeAsync() called in Mac O S X

Subject: Re: CFRunLoopRun() hangs up after ReadPipeAsync() called in Mac O S X
From: Garth Cummings <email@hidden>
Date: Fri, 22 Mar 2002 14:31:43 -0800

Hello Kane,

On Friday, March 22, 2002, at 01:19 PM, Kane Zheng wrote:

Hi, Actually I tried to use ReadPipe() first but we got error -536870168. Then the printer refused to accept/receive any data.

The return codes are in IOKit/IOReturn.h, but they're listed in hexadecimal.

If you don't have a decimal-hex converting calculator handy, you can use the GDB debugger for this. From Terminal:

% gdb
(gdb) print/x -536870168
$1 = 0xe00002e8
(gdb) quit

We have a Technical Q&A on deciphering these return codes (1075, "Making sense of I/O Kit error codes," located at <http://developer.apple.com/qa/qa2001/qa1075.html>).

Looking in IOReturn.h, you'll see that this maps to kIOReturnOverrun. So you requested less data from the device than it had to send. There were a couple of messages on the list earlier today about this very topic.

HTH,
--gc
_______________________________________________
usb mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/usb
Do not post admin requests to the list. They will be ignored.

Prev by Date: RE: CFRunLoopRun() hangs up after ReadPipeAsync() called in Mac O S X
Next by Date: Re: [OSX] Did anybody use USBLib with C++?
Previous by thread: RE: CFRunLoopRun() hangs up after ReadPipeAsync() called in Mac O S X
Next by thread: [OSX] ReadPipe error UserSpace
Index(es):
- Date
- Thread

Home