Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: test-dev@httpd.apache.org
Date: Mon, 13 Aug 2001 17:47:09 +0800 (SGT)
From: Stas Bekman <stas@stason.org>
To: Doug MacEachern <dougm@covalent.net>
Cc: <test-dev@httpd.apache.org>
Subject: Re: mod_cgi bug
In-Reply-To: <Pine.LNX.4.21.0108130033410.26617-100000@mako.covalent.net>
Message-ID: <Pine.LNX.4.33.0108131735340.24992-100000@stas.extropia.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 13 Aug 2001, Doug MacEachern wrote:

> On Mon, 13 Aug 2001, Stas Bekman wrote:
>
> > So if there is some ARGV, -d starts the gdb process via fork, a moment
> > before the test is fired, and the parent process redirects STDOUT to
> > STDERR so it won't mess up the gdb screen. or something similar, like just
> > working through the pipe in the forked process.
>
> if you can make that works so its still possible to interact with gdb
> (like making 't/TEST -b foo_function t/module/cgi.t' work), that would be
> killer.  if you mean run the test and just get a stacktrace, that would be
> cool too, there's already a Devel::CoreStack module that could be hooked
> in.  actually, i think Test::Harness already does tries that if you have
> Devel::CoreStack installed.

oh, did I volunteer to do that :) I'll give it a try

I'd probably leave the -d option as is, but add -I_am_lazy which will do
all the work for you. I want -d to work as before, because we want to
have an interactive gdb, whereas the new option will work with gdb behind
the walls.

OK for the new flag?

> > I'm sick of sending replies 'read SUPPORT' to people on the mod_perl list
> > who reports segv, without providing the calls trace. It's a known
> > fact, that people don't RTFM :(
>
> yep, me included.

if you get a chance to follow the 'mod_perl 2.0 doc project' thread, you
will see that we secretly spec out an ultra AI system, which will do all
the list's work for us. Now can we plan go skiing now?

> > Wouldn't it be cool to have ./t/TEST generate the calls trace for your on
> > segv (we already do scan for the core file), so fire gdb, generate the
> > trace and save it into a file, now use ./util/bugreport.pl and get the
> > email ready.
>
> for sure.

>> todo

> > Also did you see Devel::DebugInit::GDB on CPAN? Didn't try it yet, but it
> > says:
>
> see:
> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-05/msg02213.html
>
> i'd really like to see that working properly, but it has been
> faster/easier to get by cluttering my ~/.gdbinit by hand.

were there any changes since then?

Tell me the secret, how do you keep up with reading all these lists :(
I've hardly time to browse the new-httpd list, in addition to some 15
other lists, but I'm afraid getting on the p5p list, I'll end up reading
mails all day and no time to code :( I guess that's the price that one has
to pay if you want to be involved in perl and apache at the same time.

_____________________________________________________________________
Stas Bekman              JAm_pH     --   Just Another mod_perl Hacker
http://stason.org/       mod_perl Guide  http://perl.apache.org/guide
mailto:stas@stason.org   http://localhost/      http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/