Since this does not appear to be causing any problems for smoke tests,
I'm resolving this ticket.
No one commented unfavorably on this patch, so I suspect that the only
way we're really going to find out if it's okay is to apply it to trunk
and see if it breaks any smokes. Applied in r25376.
On Sun Jan 27 09:36:26 2008, [EMAIL PROTECTED] wrote:
Hi.
The test for the backtrace() function was failing
Could you post the failing test result?
In particular, the output of 'prove -v t/steps/auto_backtrace*.t' would
be helpful.
I haven't seen any failures in these tests lately, so I'm
On Sun, Jan 27, 2008 at 10:33:20AM -0800, James Keenan via RT wrote:
On Sun Jan 27 09:36:26 2008, [EMAIL PROTECTED] wrote:
Hi.
The test for the backtrace() function was failing
Could you post the failing test result?
In particular, the output of 'prove -v
Thanks for taking the time to work on this patch.
Since the config/auto/backtrace.pm has not generated any configuration
or build failures for me on either Linux or Darwin, the most I would be
able to say is whether it does me any harm on either of those systems.
It did no harm on Linux, where
# New Ticket Created by Art Haas
# Please include the string: [perl #50298]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=50298
Hi.
The test for the backtrace() function was failing due to the prototypes
at the
On Sunday 27 January 2008 09:36:27 Art Haas wrote:
The test for the backtrace() function was failing due to the prototypes
at the start of the test code differing for those listed in the header
file. The patch below fixes things by removing the extra prototypes
and basically copying the
