On 3/28/19 1:01 AM, Tom Lane wrote: > Andrew Dunstan <andrew.duns...@2ndquadrant.com> writes: >> I was able to get this stack trace. >> >> (gdb) bt >> #0 0x00007ffb9ce6a458 in ntdll!RtlRaiseStatus () >> from C:\WINDOWS\SYSTEM32\ntdll.dll >> #1 0x00007ffb9ce7760e in ntdll!memset () from C:\WINDOWS\SYSTEM32\ntdll.dll >> #2 0x00007ffb9ac52e1a in msvcrt!_setjmpex () >> from C:\WINDOWS\System32\msvcrt.dll >> #3 0x000000000087431a in pg_re_throw () >> at >> c:/MinGW/msys/1.0/home/pgrunner/bf/root/HEAD/pgsql.build/../pgsql/src/backend/utils/error/elog.c:1720 >> #4 0x0000000000874106 in errfinish (dummy=<optimized out>) >> at >> c:/MinGW/msys/1.0/home/pgrunner/bf/root/HEAD/pgsql.build/../pgsql/src/backend/utils/error/elog.c:464 >> #5 0x00000000007cc938 in jsonpath_yyerror (result=result@entry=0x0, >> message=message@entry=0xab0868 <__func__.110231+1592> "unrecognized flag >> of LIKE_REGEX predicate") >> at >> /home/pgrunner/bf/root/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/jsonpath_scan.l:305 >> #6 0x00000000007cec9d in makeItemLikeRegex (pattern=<optimized out>, >> pattern=<optimized out>, flags=<optimized out>, expr=0x73c7a80) >> at >> /home/pgrunner/bf/root/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/jsonpath_gram.y:512 > Hmm. Reaching the yyerror call is expected given this input, but > seemingly the siglongjmp stack has been trashed? The best I can > think of is a wild store that either occurs only on this platform > or happens to be harmless elsewhere ... but neither idea is terribly > convincing.
Further data point: if I just call the offending statement alone, there's no crash. The crash only occurs when I call the whole script. I'll see if I can triangulate a bit to get a minimal test case. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
