GNOME Bugzilla – Bug 634834
Non-latin paths
Last modified: 2011-09-24 07:02:39 UTC
Nemiver can't debug executables, the path to which contains non-latin characters: |E|bool nemiver::GDBEngine::Priv::on_gdb_stdout_has_data_signal(Glib::IOCondition):nmv-gdb-engine.cc:889:Invalid byte sequence in conversion input I think I'm not the only one who prefers naming directories in my native language, please fix. Seems that the change will be trivial: add gdb_stdout_channel->set_encoding(NULL) and gdb_stderr_channel->set_encoding(NULL) (or how this method is called in gtkmm, I don't know) in src/dbgengine/nmv-gdb-engine.cc:launch_gdb_real(). This will handle UTF-8 characters coming from these streams.
I am using UTF-8 encoding myself and Nemiver was working fine for me. I couldn't reproduce the issue by just doing nemiver ~/devel/tests/éçà/test However, I could reproduce it by doing: LANG=C LANG=C G_FILENAME_ENCODING=utf8 nemiver ~/devel/tests/éçà/test So I suppose the encoding of the file path on are passing to Nemiver is different from the encoding specified by the LANG env variable. In those case, the variable G_FILENAME_ENCODING must be set to the encoding of the path, when invoking Nemiver (or any other GNOME application that has to deal with file path). The commit 6e3ef5da12 should make Nemiver comply with that rule.
Thank you, version 0.8.1 works nice. Though I must note that when I press the "Run" button in the "Load executable" dialog with a non-latin-path executable, a GTK assertion is printed to stderr: (nemiver:2210): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed Of course, it isn't really critical.
I am glad your pain has been somewhat addressed. I think maybe this bug should be re-opened then, at least to deal with that Gtk-CRITICAL issue. No ?
Actually I don't care much about this assertion. But, considering this assertion a potential flaw in the program that could affect users in some circumstances, yes, this bug should probably be reopened.
*** Bug 640373 has been marked as a duplicate of this bug. ***
This critical issue was caused by the command view or log view, I don't remember which one. The view was displaying in a GtkTextView the output of gdb, and this output was not a valid utf8 string. Since those two views have been removed from nemiver [0], may be we can close this bug ? [0] http://git.gnome.org/browse/nemiver/commit/?id=6742800b53553dd191ace386cfc2c4681537e394
As you wish. After a fresh nemiver is available in my distro, I'll check if the error message disappeared.
Just tested 0.9.0, no warnings anymore. Thanks!