Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 21 Nov 2004 16:25:44 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: select() read() and write() on /dev/console Message-ID: <20041121212544.GB6384@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20041119183842 DOT GB26102 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sun, Nov 21, 2004 at 07:00:42PM +0100, Jason Curl wrote: >Christopher Faylor wrote: >>On Fri, Nov 19, 2004 at 06:46:56PM +0100, Jason Curl wrote: >> >>>My question, how do I go about investigating what the root cause is? Has >>>anybody else seen similar issues and been able to work around it? I'm >>>stuck and I've never seen the source code to cygwin before. >> >> >>If you suspect a problem with the cygwin DLL then you can build a >>debugging version of the cygwin DLL and debug it using gdb. >> >>Most of the console handling is in fhandler_console.cc. The select >>handling is in select.cc. Look for the string "console" there. >> >>Instructions for building the DLL are in the FAQ: >> >>http://cygwin.com/faq/faq_3.html#SEC101 >> >Hello, > >Is there a way I can use debug_printf() inside C source (not C++). I've >found and . > >Googling and I don't find information about what I need to include, and >probably what I need to link. > >#define TRACE >#include >#include > >int main(void) >{ > debug_printf("TEST\n"); >} > >It won't link, not finding _err_handler. Just use regular printf or fprintf. debug_printf is not intended for use outside of the cygwin DLL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/