verify_handle false alarm?

Pierre A. Humblet
Sun Jan 25 17:49:00 GMT 2004

At 12:17 AM 1/25/2004 -0500, you wrote:
>On Sat, Jan 24, 2004 at 04:58:42PM -0500, Pierre A. Humblet wrote:
>>Chris, your verify_handle is having an effect:
>>CYGWIN_ME-4.90 hpn5170x 1.5.8(0.110/3/2) 2004-01-24 12:54 i686 unknown
>>unknown Cygwin
>>C:\Home\Pierre>bash --login
>> 751164 [main] BASH 133894265 verify_handle: int proc_subproc(long unsigned
>> long unsigned int):328 - multiple attempts to add handle 0xC
>> 760796 [main] BASH 133894265 verify_handle:  previously allocated by void
>>oc_init():616(signal_arrived<0xAC>) winpid -133894265
>>but it looks like a false alarm: the new handle is in the space of the
>Yep.  I was a little too overzealous in my search for DuplicateHandles it
>seems.  I've removed the errant VerifyHandle.
O.K., that's fine now. 

But FYI:

CYGWIN_ME-4.90 hpn5170x 1.5.8(0.110/3/2) 2004-01-25 10:15 i686 unknown
unknown Cygwin

    133 [unknown (0xFFFD3F41)] ? -68151 munge_threadfunc: non-fatal
warning: unk
nown thread! search_for 0x61059260, cygthread::stub 0x61003340,
ad 0x61059260, possible func offset 0xBFF92876

It happened once when lauching the 1st program (rxvt) after rebuilding, and
it's not


More information about the Cygwin-developers mailing list