Hi Guys!
Another day, another try...another segfault ;-(
(gdb) run -X
Starting program: /usr/sbin/httpd -X
Program received signal SIGSEGV, Segmentation fault.
0x00e89582 in ?? ()
(gdb)
(gdb)
(gdb) BT
#0 0x00e89582 in ?? ()
#1 0x006e8c44 in ?? ()
#2 0x00000106 in ?? ()
#3 0x006b9aa6 in ?? ()
#4 0x00508940 in ?? ()
#5 0x09c59c74 in ?? ()
#6 0x41414141 in ?? ()
#7 0xbff90488 in ?? ()
#8 0x00440bdd in ?? ()
#9 0x41414141 in ?? ()
#10 0x0968542c in ?? ()
#11 0x006e89e4 in ?? ()
#12 0x09c59c74 in ?? ()
#13 0x09b89b40 in ?? ()
#14 0xbff904a8 in ?? ()
#15 0x006c7493 in ?? ()
#16 0x09c59c74 in ?? ()
#17 0x00d3a410 in ?? ()
#18 0x0968542c in ?? ()
I rewrote the smaller one of the graph-generating epl's as perl code.
This is how i call the embperl page:
[-
Execute('../call/flow-graph.epl', "$date", "src");
Execute('../call/flow-graph.epl', "$date", "dest");
-]
And this the mod_perl way:
[-
Execute({inputfile => '../call/flow-graph.pl', syntax => 'Perl', param =>
["$date", 'src']});
Execute({inputfile => '../call/flow-graph.pl', syntax => 'Perl', param =>
["$date", 'dest']});
-]
Both lead to a segfault.
BUT:
If i call flow-graph.pl directly from the browser the page works!!!
@Martien: I forwarded the mail to you too because maybe you know something about
the problem as it occurs only with your GD::Graph module.
Thanks, Alex
Von: Stas Bekman <[EMAIL PROTECTED]> am 13.11.2003 22:41
An: Gerald Richter <[EMAIL PROTECTED]>
Kopie: Alexander Hartmaier/DEBIS/EDVG/[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Thema: Re: Antwort: Re: Antwort: Re: [mp2] segfault when generating graphs
with GD::Graph under Embperl
Gerald Richter wrote:
> Hi Stas,
>
>>There is an easy way to work around it. Run the program under gdb and
>>it'll remember the trace even the memory (frames) gets corrupted.
>>
>>gdb /path/to/httpd
>>gdb> run -X
>>issue a request here and gdb will tell you that you've got a segfault
>><gdb> bt
>>will give you the trace.
>>
>
>
> This is excatly what we have done and which gives the above trace with does
> not contain any usefull informations ...
Sorry, Gerald. I've missed that detail then.
In which case you need to try to manually step through guessing some
breakpoints where things could go wrong.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
*2*
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
