Regarding debug_printf in your code base.

Hi Developers, In your code base, I can see in lot of places there are calls to debug_printf, example How do I invoke/build cygwin so that debug_printf dumps debugging information to the console. Rgrds, Abhijit -- Problem reports: http://cygwin.com/problems.html FAQ: htt

Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384

Thank you everyone for your time and reply. I believe from your reply I am able to get the problem sorted out. I would also try to reply to each of your queries @Chris J. Breisch @Warren Young Qs/Stmt: Why are you using that make and not the Cygwin make? Qs/Stmt: I suggest that you switch to CMak

Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384

Yes, MSVS is Microsoft Visual Studio. and I am using the make for Windows (http://gnuwin32.sourceforge.net/packages/make.htm). Please note, when I am saying the path is getting truncated, its the bash that is truncating it. Also, its immaterial how and what is getting called. With the latest Cygw

Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384

On a typical configuration, we use gmake on windows as the build system. GMAKE calls the Cygwin bash in order to invoke the MSVS compiler in-order to satisfy the dependency if a rule to call the compiler is present. Now, for certain modules, the command line was seemingly getting truncated. On inve