No trick. gdb under cygwin just plain sucks. So you resort to old-school debugging. You can use "cpack --debug" to get more verbose output and help narrow down where something happens. Or add cout/printf code to a build of CPack until you figure it out...
On 3/7/08, Mathieu Malaterre <[EMAIL PROTECTED]> wrote: > > Just out of curiosity, how did you track it down ? Is there a trick to > get a nice backtrace from gdb under cygwin ? > > BTW is cmake stable (I cannot access the dashboard page) right now ? > > Thanks, > -Mathieu > > > On Fri, Mar 7, 2008 at 5:08 PM, Bill Hoffman <[EMAIL PROTECTED]> > wrote: > > OK, I tracked it down. I have checked in a fix. It now produces this > > warning: > > > > CPack Warning: CPACK_CYGWIN_PATCH_NUMBER not specified using 1 > > > > > > If you set that variable your crash should go away. > > > > -Bill > > > > > > > > > > > -- > > Mathieu >
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
