https://bugs.documentfoundation.org/show_bug.cgi?id=154463

Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    Crash report or|["SwNodeIndex::SwNodeIndex( |["SwNodeIndex::SwNodeIndex(
    crash signature|SwNodeIndex const           |SwNodeIndex const
                   |&,o3tl::strong_int<long,Tag |&,o3tl::strong_int<long,Tag
                   |_SwNodeOffset>)"]           |_SwNodeOffset>)","sw::mark:
                   |                            |:FindFieldSep(sw::mark::IFi
                   |                            |eldmark
                   |                            |const&)","SwNodeIndex::SwNo
                   |                            |deIndex(SwNode *)"]
           Priority|medium                      |high

--- Comment #7 from Stéphane Guillou (stragu) 
<stephane.guil...@libreoffice.org> ---
Reproduced in recent trunk build:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 0dcaff6043e1f24ce0fa354dff80a86e40622247
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

For LO 7.2 on Linux, from comment 2, signature was
"sw::CalcBreaks(std::vector<std::pair<unsigned long, int>,
std::allocator<std::pair<unsigned long, int> > >&, SwPaM const&, bool)".

Different crash signatures in currently maintained branches:
- 7.6.6.3, "sw::mark::FindFieldSep(sw::mark::IFieldmark const&)":
https://crashreport.libreoffice.org/stats/crash_details/81d71af2-6023-4587-8f0a-2c99e82716e8
- 24.2.3.2, pesky "<name omitted>" on Linux:
https://crashreport.libreoffice.org/stats/crash_details/1f47136c-e9bc-4b6c-8fba-bd0d054aa47f
   - "SwNodeIndex::SwNodeIndex(SwNode *)" on Windows:
https://crashreport.libreoffice.org/stats/crash_details/0291707b-0649-48d3-93a8-04a9475ecbb6

(In reply to Thorsten Behrens (allotropia) from comment #6)
> Un-CCing developer, unclear if we have time to investigate this.
Upping priority then.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to