Summary: | crashtesting assert | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Caolán McNamara <caolan.mcnamara> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | caolan.mcnamara, michael.stahl, nemeth, serval2412, xiscofauli |
Priority: | medium | Keywords: | haveBacktrace |
Version: | 6.2.0.0.alpha0+ | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 105537 | ||
Attachments: | bt with debug symbols |
Description
Caolán McNamara
2018-10-15 19:07:04 UTC
Created attachment 145789 [details]
bt with debug symbols
On pc Debian x86-64 with master sources updated today, I could reproduce this.
Thought a bt with symbols may help here (+ some errors on traces just before the assert)
2759 assert(aIter1 != aRange1.second && aIter2 != aRange2.second); (gdb) p aIter1 $1 = {first = 3, second = {first = 0x55555aa6afa0, second = false}} (gdb) p aRange1.second $2 = {first = 3, second = {first = 0x55555aa6afa0, second = false}} (gdb) p aIter2 $3 = {first = 3, second = {first = 0x55555aa6afa0, second = false}} (gdb) p aRange2.second $4 = {first = 4, second = {first = 0x55555adb6e80, second = false}} this seems to have healed (In reply to Caolán McNamara from comment #3) > this seems to have healed Setting to RESOLVED WORKSFORME unless we know the commit fixing it... |