Front page | perl.perl5.porters |
Postings from November 2016
On 11/08/2016 01:20 PM, James E Keenan via RT wrote:
> On Tue, 08 Nov 2016 07:38:12 GMT, khw wrote:
>>
>> On 11/08/2016 04:37 AM, James E Keenan via RT wrote:
>>> On Tue, 08 Nov 2016 01:21:54 GMT, khw wrote:
>>>> My valgrind suggestion didn't work. Try this patch to try to force a
>>>> core dump at the time of the panic
>>> Patch apparently not attached.
>>>
>> Sorry. but here it is.
> Output is large; posted here:
>
> https://gist.github.com/jkeenan/c47a1938a668192c26e869423d9c1f66/raw/d7beb872f83dda578dba1bfaee9a355bce042023/post-khw-assert.txt
>
> But I'm not sure that told us anything new. Here's the tail of the output:
>
> #####
> Matching REx "([^\S\x{202f}\x{00a0}]+)|(\p{InFullwidth})|((?:[^\s\p{InFullwidth}]|[\x{202f}\x{00a0}])+)" against "This is "
> 0 <> <This is > | 0| 1:BRANCH(18)
> 0 <> <This is > | 1| 2:OPEN1(4)
> 0 <> <This is > | 1| 4:PLUS(16)
> | 1| ANYOF[\t\n\x0B\f\r \x85][1680 2000-200A 2028-2029 205F 3000] can match 0 times out of 2147483647...
> | 1| failed...
> 0 <> <This is > | 0| 18:BRANCH(34)
> 0 <> <This is > | 1| 19:OPEN2(21)
> 0 <> <This is > | 1| 21:ANYOF[+utf8::Texinfo::Convert::ParagraphNonXS::InFullwidth](32)
> | 1| failed...
> 0 <> <This is > | 0| 34:BRANCH(68)
> 0 <> <This is > | 1| 35:OPEN3(37)
> 0 <> <This is > | 1| 37:CURLYM[0]{1,INFTY}(66)
> 0 <> <This is > | 2| 39:BRANCH(51)
> 0 <> <This is > | 3| 40:ANYOF[^\t\n\x0B\f\r \x85\xA0{+utf8::Texinfo::Convert::ParagraphNonXS::InFullwidth}1680 2000-200A 2028-2029 202F 205F 3000](64)
> perl: util.c:1880: Perl_croak_no_modify: Assertion `0' failed.
> Aborted (core dumped)
This will help if it actually dumped a core; examining the core file
should allow you to get a stack trace. They used to be named just
'core', but maybe it is something else besides nowadays, like perl.core
or core.perl. I do it so infrequently I have to look it up each time.
Be sure your perl is compiled with -DDEBUGGING, and -D'optimize=-ggdb3'
-A'optimize=-ggdb3' -A'optimize=-O0'
That will make the back trace more readable.
It looks like the man page of gdb says you can say
gdb /path/to/perl /path/to/core
and then use the bt command to print the stack.
If this doesn't work, someone on irc can advise you
#####
> Thank you very much.
>
>
>
Thread Previous
|
Thread Next