Issue 114772 - assertion: rtl_string2UString_status() - UTF8 test encoding is wrong
Summary: assertion: rtl_string2UString_status() - UTF8 test encoding is wrong
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: DEV300m88
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2010-09-27 11:27 UTC by 400guy
Modified: 2013-01-29 21:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description 400guy 2010-09-27 11:27:55 UTC
I am running a non-product build of DEV300_m88.

One way provoke the assertion ...

(*) Create new spreadsheet.

(*) Type F4 to open datasource window.

(*) In datasource window, expand Bibliography > Tables and click on biblio. 
Program about sixty times presents Debug Output ...

    Error: rtl_string2UString_status() - UTF8 test encoding is wrong
    From File ustring.c at Line 633
    Abort ? (Yes=abort / No=ignore / Cancel=core dump)

Each time OOo regains focus, it raises the assertion some more times.
Dragging the table into cell A1 raises the assertion scores of times.

Opening the table in Base also provokes the assertion scores of times.

My decision to file this issue against module extras rather than sal
is just a guess.

Just for the benefit of anybody who "corrects" the text of the
assertion when searching the bug database, let me type in ...

    UTF8 text encoding is wrong
Comment 1 Olaf Felka 2010-09-27 11:35:08 UTC
What makes you think that this is an installation problem? No installation -> no
Comment 2 400guy 2010-09-27 12:18:29 UTC
First level answer ...

Component "installation" resulted because under the heading 
"By Code Module"
I selected component "extras"

Which I did because ...

The assertion is raised in function rtl_string2UString_status() in
sal/rtl/source/ustring.c, and the statement reads

    OSL_ENSURE( ((unsigned char)*pStr) <= 127,
                "rtl_string2UString_status() - UTF8 test encoding is wrong" );

{OpenGrok found biblio.dbf in extras/source/database/, providing another
possible component to file the issue.

On the surface, the assertion looks plausible to me, so I picked on
"extras".  Like I said, just a guess.