gnupic: Re: [gnupic] Gtk-CRITICAL in GUI gpsim
Subject:
Re: [gnupic] Gtk-CRITICAL in GUI gpsim
From:
"Nestor A. Marchesini" ####@####.####
Date:
30 Nov 2006 04:25:13 +0000
Message-Id: <456E5D2F.3090603@xinet.com.ar>
Hi Robert
I have solved the problem.
(gpsim:13571): Gtk-CRITICAL **: gtk_text_buffer_emit_insert:
assertion`g_utf8_validate (text, len, NULL)' failed
The problem they were not the GTK, It was in my locale, I use es_AR.UTF-8
[nestor@deselectronica ~]$ locale
LANG=es_AR.UTF-8
LC_CTYPE=es_AR.UTF-8
LC_NUMERIC=es_AR.UTF-8
LC_TIME=es_AR.UTF-8
LC_COLLATE=es_AR.UTF-8
LC_MONETARY=es_AR.UTF-8
LC_MESSAGES=es_AR.UTF-8
LC_PAPER=es_AR.UTF-8
LC_NAME=es_AR.UTF-8
LC_ADDRESS=es_AR.UTF-8
LC_TELEPHONE=es_AR.UTF-8
LC_MEASUREMENT=es_AR.UTF-8
LC_IDENTIFICATION=es_AR.UTF-8
LC_ALL=
[nestor@deselectronica ~]$ locale charmap
UTF-8
To change the locale in Mandriva2007 it is possible to use drakconf.
The spanish language, there uses the codification of characters ISO-8859-1
and the spanish with the symbol of the euro (EUR) the ISO-8859-15.
My original code was in ISO-8859-1 and it turns out that my linux
Mandriva2007
for default is UTF-8, in short, the problem they were the accents used
in the
commentaries of my code.
Now I use iconv to turn of format and the probema disappeared completely.
I to want to be grateful on a post in the last days, since I have
Mandriva2007
and it had the same problem of which on having wanted to change the size of
window of the RAM memory and of the window EEPROM memory it was closed gpsim
giving me a violation of segment.
Unload the libary gtk+extra-2.1.1.tar.gz and to modify the line 4152 as says
in the link passed and I can say this it was exactly the problem since now
gpsim it me works perfectly.
The steps were:
[nestor@deselectronica ~]$ tar /xvfz /gtk+extra-2.1.1.tzr.gz
[nestor@deselectronica ~]$ cd gtk+extra-2.1.1
[nestor@deselectronica ~]$ cd gtkextra
[nestor@deselectronica ~]$ cooledit --look cool gtksheet.c
change g_free(sheet->pixmap)
to g_object_unref(sheet->pixmap)
[nestor@deselectronica ~]$ ./configure
[nestor@deselectronica ~]$ make
[nestor@deselectronica ~]$ su
[root@deselectronica nestor]# make install
[root@deselectronica nestor]# cp
/usr/local/lib/pkgconfig/gtkextra-2.0.pc /usr/lib/pkgconfig
[root@deselectronica nestor]# cooledit --look cool /etc/ld.so.conf
add a line at the end with:
/usr/local/lib
[root@deselectronica nestor]# ldconfig
[root@deselectronica nestor]# exit
[nestor@deselectronica ~]$ tar xvfz gpsim-0.22.0.tzr.gz
[nestor@deselectronica ~]$ cd gpsim-0.22.0
[nestor@deselectronica ~]$ ./configure --enable-sockets
[nestor@deselectronica ~]$ make
[nestor@deselectronica ~]$ su
[root@deselectronica nestor]# make install
[root@deselectronica nestor]# ldconfig
[root@deselectronica nestor]# exit
From already thank yours and I hope that this commentary serves someone.
Regards
Néstor A. Marchesini
Chajari-Entre Rios-Argentina
ICQ # 50983752 colo
MSN ####@####.####
####@####.####
####@####.####
http://www.deselectronica.com.ar
Rob Pearce escribió:
> On Saturday 29 July 2006 08:30, Nestor A. Marchesini wrote:
>> Hi..I have a problem with gpsim,
>
> You'd be better asking on the GPSim list, so I've CC'd this reply.
>
>> From the terminal I can simulate without problems, but from the
>> graphical GUI It displeases
>> the line to executing (showed with the black arrow) with regard to the
>> line of code that is
>> executed really, the message that gives me is the following one:
>>
>> [nestor@deselectronica test]$ gpsim -s test.cod
>>
>> gpsim - the GNUPIC simulator
>> version: Release 0.21.12-pre
>>
>>
>> type help for help
>> **gpsim> SimulationMode:82
>> No long symbol table info
>> FIXME: HLL files are not supported at the moment
>> SSPADD in unimplemented, as is all of I2C.
>>
>> (gpsim:13571): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion
>> `g_utf8_validate (text, len, NULL)' failed
>>
>> That will be happening?
>>
> Which versions of GTK+ and GTK-extra are you using?
> I have GTK+ 2.8.19 and GTKextra 2.1.1
> Old versions had incompatibilities and will not work with GPSim.
>
> That said, the current PC marker does sometimes get offset for other reasons,
> such as the COD file having been built from a different version of the
> source. The release version of gplink has some defects in the reporting of
> line numbers when multiple source files and multiple code sections are used,
> which also causes similar errors on the GPSim display.
>
> Hope that helps,
> Rob Pearce
