Summary: | app-editors/pluma-1.24.1 : /.../sh:line <snip>: <snip> Segmentation fault itstool -m ${mo} ${d}/C/index.docbook ${d}/C/legal.xml | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo MATE Desktop <mate> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | chris, gentoo, sac, StormByte |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
app-editors:pluma-1.24.1:20200925-231029.log emerge-history.txt environment etc.portage.tbz2 logs.tbz2 temp.tbz2 stack trace |
Description
Toralf Förster
2020-09-26 07:00:54 UTC
Created attachment 662482 [details]
emerge-info.txt
Created attachment 662485 [details]
app-editors:pluma-1.24.1:20200925-231029.log
Created attachment 662488 [details]
emerge-history.txt
Created attachment 662491 [details]
environment
Created attachment 662494 [details]
etc.portage.tbz2
Created attachment 662497 [details]
logs.tbz2
Created attachment 662500 [details]
temp.tbz2
mate-applets 1.24.1 is also triggering the same segfault for me Weird. I'm not able to reproduce it for either of those packages. Let me try to get a backtrace of that segfault. (In reply to Adam Feldman from comment #9) > Weird. I'm not able to reproduce it for either of those packages. My segfault is in /usr/bin/python3.7m. Which python3 are you using? I currently have a slightly outdated python-3.7.7-r2 as the python being used for the single_target. What are you two using? (In reply to Adam Feldman from comment #12) > I currently have a slightly outdated python-3.7.7-r2 as the python being > used for the single_target. What are you two using? Just upgraded to 3.7.8-r2 and still no segfault here 3.7.9, 3.8.5, and 3.8.6 all segfault for me. also confirming this seems to be a regression in 1.24.1, pluma 1.24.0 still builds Created attachment 662698 [details]
stack trace
My stack trace is a bit more verbose: The top few entries show: #0 0x00007ff4fe6e2524 in function_code_fastcall (co=<optimized out>, args=0x7ff4edf77700, nargs=2, globals=<optimized out>) at Objects/call.c:280 #1 0x00007ff4f03c6566 in libxml_xmlErrorFuncHandler (ctx=<optimized out>, msg=<optimized out>) at /usr/src/debug/dev-libs/libxml2-2.9.10-r3/libxml2-2.9.10/python/libxml.c:1644 #2 0x00007ff4f0264674 in xmlParserPrintFileContextInternal (input=input@entry=0x5619fa6f5fb0, channel=channel@entry=0x7ff4f03c6420 <libxml_xmlErrorFuncHandler>, data=data@entry=0x0) at /usr/src/debug/dev-libs/libxml2-2.9.10-r3/libxml2-2.9.10/error.c:208 #3 0x00007ff4f0264a1e in xmlReportError (err=err@entry=0x5619fa7ea1a8, ctxt=ctxt@entry=0x5619fa7e9f50, str=str@entry=0x5619fa807810 "Opening and ending tag mismatch: guibutton line 0 and para\n", channel=0x7ff4f03c6420 <libxml_xmlErrorFuncHandler>, channel@entry=0x0, data=data@entry=0x0) at /usr/src/debug/dev-libs/libxml2-2.9.10-r3/libxml2-2.9.10/error.c:406 #4 0x00007ff4f02661f7 in __xmlRaiseError (schannel=schannel@entry=0x0, channel=0x7ff4f0264ff0 <xmlParserError__internal_alias>, channel@entry=0x0, data=0x5619fa7e9f50, data@entry=0x0, ctx=ctx@entry=0x5619fa7e9f50, nod=nod@entry=0x0, domain=domain@entry=1, code=76, level=XML_ERR_FATAL, file=<optimized out>, line=1, str1=<optimized out>, str2=<optimized out>, str3=<optimized out>, int1=0, col=327, msg=<optimized out>) at /usr/src/debug/dev-libs/libxml2-2.9.10-r3/libxml2-2.9.10/error.c:633 #5 0x00007ff4f026a1c5 in xmlFatalErrMsgStrIntStr (ctxt=ctxt@entry=0x5619fa7e9f50, error=error@entry=XML_ERR_TAG_NAME_MISMATCH, msg=msg@entry=0x7ff4f0347c58 "Opening and ending tag mismatch: %s line %d and %s\n", str1=<optimized out>, val=<optimized out>, str2=str2@entry=0x5619fa807287 "para") at /usr/src/debug/dev-libs/libxml2-2.9.10-r3/libxml2-2.9.10/parser.c:720 #6 0x00007ff4f0278ffb in xmlParseEndTag2 (ctxt=ctxt@entry=0x5619fa7e9f50, prefix=0x0, URI=0x5619fa80728c "http://docbook.org/ns/docbook", nsNr=0, tlen=0, line=<optimized out>) at /usr/src/debug/dev-libs/libxml2-2.9.10-r3/libxml2-2.9.10/parser.c:9682 Notice the "Opening and ending tag mismatch" message. Patch found in bug #745162 address this issue. commenting as i had this problem as well, strangely enough it compiled fine on 2 of my kaby lake intels, but always fails on my threadripper 2950x. just an update on my end, mate-applets also failed to compile on my threadripper with the same segfault. Patch from 745162 fixed issue for me too. Both for pluma and mate-applets *** This bug has been marked as a duplicate of bug 745162 *** |