Re: Debugging FastCGI

In my fastcgi development I am using citrix/xen servers with apache  
servers talking to fastcgi apps.   In order to make some sense out of  
the logs that can be generated i always setup vms to forward messages  
to a separate server (not running anything else).  It consolidates  
all of my logging without making it any more difficult to manage.   
What I really like about syslog is that you can set the limits on how  
big the files grow to, etc.  really sweet.

And whenever I am forced (and I mean __FORCED__) to do windows  
programming,  i use one of the third party apps for exporting window  
log messages to a syslog server...



On Jul 13, 2010, at 11:08 AM, [email protected] wrote:

>
> I've been having good success just dumping everything to syslog,  
> which is obviously a unix construct but I have the log file viewer  
> open and just run it, and it works out to be faster for me than  
> even doing C# / ASP.NET debugging and setting breakpoints.  My site  
> is up at http://www.mightyware.com, and its a nutty mix of stuff,  
> but the whole thing is a fastcgi app with all the .bhs pages are  
> just text files filtered by the fastcgi.  Works pretty well. I  
> debug it on my ubuntu box and then deploy it up to my linode and I  
> just love it.
>
> -------- Original Message --------
> Subject: FastCGI-developers_Digest,_Vol_24,_Issue_2
> From: fastcgi-developers-request-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> Date: Tue, July 13, 2010 12:00 pm
> To: fastcgi-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
>
> Send FastCGI-developers mailing list submissions to
> fastcgi-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers
> or, via email, send a message with subject or body 'help' to
> fastcgi-developers-request-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
>
> You can reach the person managing the list at
> fastcgi-developers-owner-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of FastCGI-developers digest..."
>
>
> Today's Topics:
>
> 1. The right way to debug a FastCGI app (Wes Widner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 12 Jul 2010 15:41:32 -0400
> From: Wes Widner <[email protected]>
> Subject: [FASTCGI] The right way to debug a FastCGI app
> To: fastcgi-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> Message-ID:
> <AANLkTinsxwwPRFY0yNSKOfbwmXDzivMjEWJeWV1PRYTt-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello,
>
> I've recently written an application using the FastCGI framework  
> (in C) and
> I've been very impressed with the speed it offers. However when I  
> went to
> write an extension to my application I've run into some difficulties
> debugging my code so I wanted to see if anyone here had a better  
> idea of how
> to go about debugging a FastCGI application.
>
> Here is what I am attempting to do thus far:
> Run cgi-fcgi through gdb: gdb cgi-fcgi
> Then run my fastcgi application directly: (gdb) r -start -connect
> 127.0.0.1:9005 ./myapp.fcgi 1
>
> This produces the output:
> Starting program: /usr/bin/cgi-fcgi -start -connect 127.0.0.1:9005
> ./*myapp*.fcgi
> 1
> [Thread debugging using libthread_db enabled]
>
> Program exited normally.
>
> Is this the right approach? If so, what am I doing wrong? If not,  
> what is
> the best way to go about debugging my application?
>
> Thanks in advance,
> -Wes
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.pins.net/mailman/private.cgi/fastcgi- 
> developers/attachments/20100712/447407e3/attachment-0001.html>;
>
> ------------------------------
>
> _______________________________________________
> FastCGI-developers mailing list
> FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers
>
>
> End of FastCGI-developers Digest, Vol 24, Issue 2
> *************************************************
> _______________________________________________
> FastCGI-developers mailing list
> FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers

_______________________________________________
FastCGI-developers mailing list
FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers