Does anyone debug Wt applications on Mac OS X?  As described below, when 
running under gdb 6.3.5, as soon as I type ^C, my Wt application shuts down.  
As a result, whenever I want to set a new breakpoint, I have to restart my 
application, which requires logging in again.

Are there any workarounds for this?

Begin forwarded message:

> From: Joseph VanAndel <[email protected]>
> Date: July 22, 2010 9:44:18 AM MDT
> To: [email protected]
> Subject: [Wt-interest] debugging Wt application on Mac OS 10.6.4, vs CentOS 
> 5.5
> Reply-To: [email protected]
> 
> I'm trying to debug my Wt 3.1.3 application on both OS 10.6.4, and CentOS 5.5.
> 
> If I use the stock Wt 3.1.3 library on either platform, as soon as I type 
> '^C' in gdb, the application shuts down.
> 
> I've rebuild Wt 3.1.3 on both platforms with the change:
> 
> Wt::waitForShutdown(const char *restartWatchFile)
> 
> ,
> .
> .
>  sigaddset(&wait_mask, SIGHUP);   // catching SIGHUP messes up gdb!
>  /*
>   * uncomment SIGINT when experiencing annoying gdb interference
>   */
>  // sigaddset(&wait_mask, SIGINT); // DISABLED to allow debugging
>  sigaddset(&wait_mask, SIGQUIT);
>  sigaddset(&wait_mask, SIGTERM);
>  pthread_sigmask(SIG_BLOCK, &wait_mask, 0);
> 
> .
> .
> }
> [ BTW: shouldn't the comment be '*comment out*' SIGINT when experiencing 
> annoying gdb interference ???]
> 
> 
> 
> On CentOS 5.5, I can interrupt the application in the debugger, set 
> breakpoints, and continue.
> 
> On OS 10.6.4, my application always shuts down, whether I use the "continue" 
> command or "signal 0":
> 
> Program received signal SIGINT, Interrupt.
> 0x00007fff886c6b3e in __sigwait ()
> (gdb) signal 0
> Continuing with no signal.
> [2010-Jul-22 09:38:46.055333] 17852 - [notice] "Shutdown (signal = 1)"
> [2010-Jul-22 09:38:46.055513] 17852 - [notice] "Shutdown: stopping sessions."
> [2010-Jul-22 09:38:46.058301] 17852 [/ nTUjQTvXIN8CdltE] [notice] "Session 
> destroyed (#sessions = 0)"
> 128.117.85.186 - - [2010-Jul-22 09:38:46.058529] "POST 
> /?wtd=nTUjQTvXIN8CdltE&rand=43338 HTTP/1.1" 200 0
> execve: Operation timed out
> 
> Program exited normally.
> 
> -------------
> Any work-arounds for debugging on Mac OS 10.6?
> 
> (I tried "handle SIGINT stop nopass" - it doesn't help.)
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to