FAQ
Hello,

The question was already asked in the list, but I can't remember of any
satisfying answer.

Did anybody succeed in running the standalone server in debug mode ?

Seems that the server main loop, waiting for HTTP events, is not
compatible with the debugger loop waiting for keyboard events.
I'm able to set breakpoints after Catalyst has loaded all modules and
just before entering MyApp->run($port, $host ...) .. but the breakpoints
never actually break.

Thanks in advance, L. Dami

PS I'm running perl v5.8.8 built for MSWin32-x86-multi-thread, Binary
build 819 [267479] provided by ActiveState


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20070427/f0dcb814/attachment.htm

Search Discussions

  • Rahed at Apr 27, 2007 at 3:05 pm

    "Dami Laurent (PJ)" <laurent.dami@justice.ge.ch> writes:

    Did anybody succeed in running the standalone server in debug mode ?
    I run it as perl -d myapp_server.pl though it's on Solaris, not on
    Windows.

    --
    Radek
  • Michael Reece at Apr 27, 2007 at 5:24 pm
    i usually stick $DB::single=1 at the top of the controller method i
    am debugging, then perl -d ./script/myapp_server.pl
    it then drops to the debugger prompt after i make the http request.
    On Apr 27, 2007, at 5:04 AM, Dami Laurent ((PJ)) wrote:

    Hello,

    The question was already asked in the list, but I can't remember of
    any satisfying answer.

    Did anybody succeed in running the standalone server in debug mode ?

    Seems that the server main loop, waiting for HTTP events, is not
    compatible with the debugger loop waiting for keyboard events.

    I'm able to set breakpoints after Catalyst has loaded all modules
    and just before entering MyApp->run($port, $host ...) .. but the
    breakpoints never actually break.

    Thanks in advance, L. Dami

    PS I'm running perl v5.8.8 built for MSWin32-x86-multi-thread,
    Binary build 819 [267479] provided by ActiveState


    _______________________________________________
    List: Catalyst@lists.rawmode.org
    Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
    Searchable archive: http://www.mail-archive.com/
    catalyst@lists.rawmode.org/
    Dev site: http://dev.catalyst.perl.org/
    ---
    michael reece :: software engineer :: mreece@vinq.com


    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20070427/270b88e8/attachment-0001.htm
  • Kieren Diment at Apr 28, 2007 at 10:37 am
    http://dev.catalyst.perl.org/wiki/DebugSample
    On 27/04/07, Dami Laurent (PJ) wrote:

    Hello,

    The question was already asked in the list, but I can't remember of any
    satisfying answer.

    Did anybody succeed in running the standalone server in debug mode ?

    Seems that the server main loop, waiting for HTTP events, is not
    compatible with the debugger loop waiting for keyboard events.

    I'm able to set breakpoints after Catalyst has loaded all modules and just
    before entering MyApp->run($port, $host ...) .. but the breakpoints never
    actually break.

    Thanks in advance, L. Dami

    PS I'm running perl v5.8.8 built for MSWin32-x86-multi-thread, Binary
    build 819 [267479] provided by ActiveState


    _______________________________________________
    List: Catalyst@lists.rawmode.org
    Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
    Searchable archive:
    http://www.mail-archive.com/catalyst@lists.rawmode.org/
    Dev site: http://dev.catalyst.perl.org/
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20070428/6b659c78/attachment-0001.htm

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcatalyst @
categoriescatalyst, perl
postedApr 27, '07 at 1:04p
activeApr 28, '07 at 10:37a
posts4
users4
websitecatalystframework.org
irc#catalyst

People

Translate

site design / logo © 2022 Grokbase