On Thu, 2 Aug 2001, Stas Bekman wrote:

> Ok, so with the latest workaround the normal run of 'make test' succeeds
> on my machine. But, if I stress-test, I see segfaults:
>
> % ./t/TEST -order=random -times=5
>
> ...
> apr/base64..............malformed response at
> /home/stas/apache.org/modperl-2.0-perlmodule/blib/lib/Apache/TestRequest.pm
> line 241.
> FAILED before any test output arrived
> ...
> apr/pool................malformed response at
> /home/stas/apache.org/modperl-2.0-perlmodule/blib/lib/Apache/TestRequest.pm
> line 241.
> FAILED before any test output arrived
> ...
> api/server_rec..........FAILED before any test output arrived
> api/uri.................FAILED before any test output arrived
> api/server_rec..........FAILED before any test output arrived
> ...
> api/server_rec..........malformed response at
> /home/stas/apache.org/modperl-2.0-perlmodule/blib/lib/Apache/TestRequest.pm
> line 241.
> FAILED before any test output arrived
>
> ./t/TEST -debug
> behaves weirdly:
>
> % ./t/TEST -debug
> GNU gdb 5.0mdk-11mdk Linux-Mandrake 8.0
> Copyright 2001 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i386-mandrake-linux"...
> [New Thread 1024 (LWP 27654)]
> [New Thread 2049 (LWP 27664)]
> [New Thread 1026 (LWP 27665)]
> Delayed SIGSTOP caught for LWP 27665.
> Received Real-time signal 0 in LWP 27654 while waiting for SIGSTOP.
> [New Thread 2051 (LWP 27666)]
> Using pending wait status for LWP 27654.
> Delayed SIGSTOP caught for LWP 27666.
> LWP 27665 exited.
>
> I thought to catch the segfaults with the combination of:
> % ./t/TEST -debug
> % ./t/TEST -run
> in 2 different consoles
>
> but that doesn't seem to work, the debug console just hangs with the
> output above

Hmm, after all it does work (I want to understand the notes about SIGSTOP
when I run with -debug),

here is the first one:

....
apr/base64.............. <-segfault

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 2051 (LWP 27666)]
0x403875f3 in mpxs_ap_rvputs (my_perl=0x82211a8, items=2, mark=0x861fe88,
    sp=0x861fe88)
    at
/home/stas/apache.org/modperl-2.0-perlmodule/xs/Apache/RequestIO/Apache__RequestIO.h:37
37          rcfg = modperl_config_req_get(r);
(gdb) where
#0  0x403875f3 in mpxs_ap_rvputs (my_perl=0x82211a8, items=2,
mark=0x861fe88,
    sp=0x861fe88)
    at
/home/stas/apache.org/modperl-2.0-perlmodule/xs/Apache/RequestIO/Apache__RequestIO.h:37
#1  0x403894b4 in XS_Apache__RequestRec_PRINT (my_perl=0x82211a8,
cv=0x8241ac0)
    at RequestIO.xs:137
#2  0x402aaa40 in Perl_pp_entersub (my_perl=0x82211a8) at pp_hot.c:2715
#3  0x402a048f in Perl_runops_debug (my_perl=0x82211a8) at run.c:53
#4  0x40237910 in S_call_body (my_perl=0x82211a8, myop=0xbf5fd5cc,
is_eval=0)
    at perl.c:1861
#5  0x4023704f in Perl_call_sv (my_perl=0x82211a8, sv=0x869aecc, flags=64)
    at perl.c:1740
#6  0x40236d7c in Perl_call_method (my_perl=0x82211a8,
    methname=0x4033cc44 "PRINT", flags=0) at perl.c:1673
#7  0x402a2afd in Perl_pp_print (my_perl=0x82211a8) at pp_hot.c:576
#8  0x402a048f in Perl_runops_debug (my_perl=0x82211a8) at run.c:53
#9  0x40237910 in S_call_body (my_perl=0x82211a8, myop=0xbf5fd7ec,
is_eval=0)
    at perl.c:1861
#10 0x402374b2 in Perl_call_sv (my_perl=0x82211a8, sv=0x859174c, flags=4)
    at perl.c:1779
#11 0x40229958 in modperl_callback (my_perl=0x82211a8, handler=0x868f62c,
    p=0x8387c74, s=0x80ddd94, args=0x869ae90) at modperl_callback.c:52
#12 0x4022a017 in modperl_callback_run_handlers (idx=6, type=3,
r=0x8387ca4,
    c=0x0, s=0x80ddd94, pconf=0x0, plog=0x0, ptemp=0x0)
    at modperl_callback.c:166
#13 0x4022a0ee in modperl_callback_per_dir (idx=6, r=0x8387ca4)
    at modperl_callback.c:190
#14 0x40225e3e in modperl_response_handler_run (r=0x8387ca4, finish=1)
    at mod_perl.c:422
#15 0x40225edd in modperl_response_handler (r=0x8387ca4) at mod_perl.c:441
#16 0x080782b7 in ap_run_handler (r=0x8387ca4) at config.c:185
#17 0x08078753 in ap_invoke_handler (r=0x8387ca4) at config.c:344
#18 0x08068a8f in process_request_internal (r=0x8387ca4) at
http_request.c:378
#19 0x08068b70 in ap_process_request (r=0x8387ca4) at http_request.c:444
#20 0x08064f59 in ap_process_http_connection (c=0x8130c4c) at
http_core.c:287
#21 0x08080107 in ap_run_process_connection (c=0x8130c4c) at
connection.c:82
#22 0x080762a5 in process_socket (p=0x8130b4c, sock=0x8130b7c,
my_child_num=0,
    my_thread_num=0) at threaded.c:470
#23 0x08076626 in worker_thread (thd=0x811128c, dummy=0x82eae68)
    at threaded.c:631
#24 0x0809f931 in dummy_worker (opaque=0x811128c) at thread.c:122
#25 0x40099c84 in pthread_start_thread_event (arg=0xbf5ffc00) at
manager.c:274




_____________________________________________________________________
Stas Bekman              JAm_pH     --   Just Another mod_perl Hacker
http://stason.org/       mod_perl Guide  http://perl.apache.org/guide
mailto:[EMAIL PROTECTED]   http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to