After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 310118 - How to handle strange encoding for ole2 property set
How to handle strange encoding for ole2 property set
Status: RESOLVED INCOMPLETE
Product: libgsf
Classification: Core
Component: MS OLE2 & Properties
1.12.x
Other All
: High minor
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2005-07-12 13:05 UTC by Alexandre Bonneau
Modified: 2013-02-23 21:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
strace gnumeric crashing. output1 is "1>" and output2 is "2>". (85.27 KB, application/bzip2)
2005-07-12 13:07 UTC, Alexandre Bonneau 		Details

Description Alexandre Bonneau 2005-07-12 13:05:34 UTC 
Distribution/Version: Debian unstable

As soon as I want to save a specific Excel file I worked on with Gnumeric since 
a week, it crash.
Comment 1 Alexandre Bonneau 2005-07-12 13:07:36 UTC 
Created attachment 49014 [details]
strace gnumeric crashing. output1 is "1>" and output2 is "2>".

Here is the strace from the crash.
Comment 2 Jean Bréfort 2005-07-14 13:35:38 UTC 
It would help a lot if you could provide a stack trace and a sample excel file.
Comment 3 Alexandre Bonneau 2005-07-14 14:20:04 UTC 
The stack trace is already posted.
Concerning the sample excel file, and due to confidential status, only jody got 
it.
Comment 4 Jon Kåre Hellan 2005-07-14 15:24:43 UTC 
strace makes a log of system calls the program makes - reads, writes, stats, etc.
With the debugger, you can make a stack trace, which is something else. It tells
at what program line the program crashed, how it got there, and values of
variables. Here's how to make one (you type the commands at the shell and (gdb)
prompts):

$ gdb gnumeric
(gdb) r
<wait for crash

Program received signal SIGSEGV, Segmentation fault.

+ Trace 61744

Thread 16384 (LWP 17503)

  • #0 wbcg_copy_toolbar_visibility
    at workbook-control-gui.c line 1830
  • #1 gui_wb_view_show
    at gui-file.c line 110
  • #2 gui_file_read
    at gui-file.c line 136
  • #3 cb_file_history_activate
    at wbc-gtk.c line 711
  • #4 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 _gtk_action_emit_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0 

(gdb) quit

But if Jody can replicate with the file you sent, we're not going to need it.
Comment 5 Jody Goldberg 2005-07-30 15:52:44 UTC 
I get a crash in libgsf's property export and some warnings on import
Patching the crash is simple, but there's a problem importing property arrays
with strings in cyrilic.
Comment 6 Jody Goldberg 2005-07-31 02:48:11 UTC 
The problem stems from strangely encoded text.  It claims to be in codepage 1251
(ms cyrilic) but somehow
     d0 a0 c2 a4 d0 a0 d1 91 d0 a0 c2 bb d0 a0 d1 98
produces
    'Филм'
Comment 7 Morten Welinder 2013-01-05 00:13:26 UTC 
Do we have a copy of this file?
Comment 8 Morten Welinder 2013-02-23 21:46:34 UTC 
We seem to have lost the file and therefore cannot work on this.  Feel
free to reopen if the file resurfaces.