Re: Unhandled exception?

[Phillip Susi <psusi ubuntu com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/22/2014 12:52 PM, Kjell Ahlstedt wrote:
> The gtkmm tutorial contains a section that describes how to use the gdb debugger to see where an exception 
> is thrown in a signal handler.
>
> https://developer.gnome.org/gtkmm-tutorial/stable/sec-exceptions-in-signal-handlers.html.en

Thanks... so it seems the problem is that Glib::IOChannel::read() is throwing the exception because dosfsck 
is spitting out a 0xBD character.  It seems that in CP 437, that is a 1/2 chracter, but in UTF-8 it is an 
incomplete multi byte sequence.  This leads me to conclude that there is a bug in glibmm, and I have a 
question on how to handle this character.  The question is how to have IOChannel::read treat its input as 
CP-437 instead of UTF-8, and the bug:

glibmm seems to have an automatic exception catch that prints a warning and attempts to continue.  This is 
wrong.  An unhandled exception should terminate the program.  By eating the exception, glibmm has caused 
gparted's call stack to unwind leaving the program in a broken state.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTg5ATAAoJEI5FoCIzSKrwUPQH/Rwsqgc3aHTUngiJRqQ+1+2S
wSniICWVoS3ZbobVuMe5d1L9yQcCfwFJFM1pK1KftVUnJqxShtnENRqWSu6UZH2p
04oxdJMiKv57xZPyMWZET2gvAN5t2AcMOUW0IgQr0yIBJkOR8mWfT9H4yH3JJ1Wr
SnLehkyRwzwdgqEDAUWCK/wwuVOJUv6KUmlDUZ7niX/h/bWTRPZWlH4aeI8MXjo5
KPptkvaJCrQUUoFUEAtVuEq+gsjuLN5bf51RBI46ZQkOvfvDVeOO4HswI6xOu4M6
bP37TqmaG6qLe0bv+bhFTIenrzddXzwx9sOWcSdc6ivyHPrv9+T45Nv+xPIMjKY=
=bDGy
-----END PGP SIGNATURE-----