Bug#595271: gedit crash when saving empty file

[Mathieu Malaterre]

On Thu, Sep 16, 2010 at 9:54 PM, Mathieu Malaterre
<mathieu.malaterre at gmail.com> wrote:
> On Thu, Sep 16, 2010 at 7:58 PM, Josselin Mouette <joss at debian.org> wrote:
>> Le jeudi 16 septembre 2010 à 19:14 +0200, Mathieu Malaterre a écrit :
>>> sudo apt-get install libc6
>>> ...
>>>
>>> I can still get the crash:
>>
>> Could you paste the new backtrace? I’d like to see where exactly.
>

If this is of any importance, I can run gedit using valgrind, in this
case I do not get a crash:

$ valgrind --db-attach=yes gedit
==3144== Memcheck, a memory error detector
==3144== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==3144== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for
copyright info
==3144== Command: gedit
==3144==
==3144== Conditional jump or move depends on uninitialised value(s)
==3144==    at 0xC282290: inflateReset2 (in /usr/lib/libz.so.1.2.3.4)
==3144==    by 0xC28237F: inflateInit2_ (in /usr/lib/libz.so.1.2.3.4)
==3144==    by 0xC27BC86: ??? (in /usr/lib/libz.so.1.2.3.4)
==3144==    by 0x63430B5: ??? (in /usr/lib/libxml2.so.2.7.6)
==3144==    by 0x6342AA7: __xmlParserInputBufferCreateFilename (in
/usr/lib/libxml2.so.2.7.6)
==3144==    by 0x63C7114: xmlNewTextReaderFilename (in
/usr/lib/libxml2.so.2.7.6)
==3144==    by 0x7490765: ??? (in /usr/lib/libgnomevfs-2.so.0.2200.0)
==3144==    by 0x7490CCC: gnome_vfs_mime_get_value (in
/usr/lib/libgnomevfs-2.so.0.2200.0)
==3144==    by 0x444DF9: _gedit_tab_get_tooltips (in /usr/bin/gedit)
==3144==    by 0x46A02C: ??? (in /usr/bin/gedit)
==3144==    by 0x46A869: gedit_notebook_add_tab (in /usr/bin/gedit)
==3144==    by 0x44EBCC: gedit_window_create_tab (in /usr/bin/gedit)
==3144==
==3144==
==3144== ---- Attach to debugger ? --- [Return/N/n/Y/y/C/c] ----
==3144==
==3144== HEAP SUMMARY:
==3144==     in use at exit: 3,373,253 bytes in 31,410 blocks
==3144==   total heap usage: 206,835 allocs, 175,425 frees, 24,348,423
bytes allocated
==3144==
==3144== LEAK SUMMARY:
==3144==    definitely lost: 86,140 bytes in 285 blocks
==3144==    indirectly lost: 144,282 bytes in 4,441 blocks
==3144==      possibly lost: 1,922,261 bytes in 12,901 blocks
==3144==    still reachable: 1,220,570 bytes in 13,783 blocks
==3144==         suppressed: 0 bytes in 0 blocks
==3144== Rerun with --leak-check=full to see details of leaked memory
==3144==
==3144== For counts of detected and suppressed errors, rerun with: -v
==3144== Use --track-origins=yes to see where uninitialised values come from
==3144== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 20 from 8)

-- 
Mathieu