gnupic: gpsim-0.20.9b
Subject:
Re: gpsim-0.20.9b
From:
Scott Dattalo ####@####.####
Date:
25 Jul 2001 13:31:02 -0000
Message-Id: <Pine.LNX.4.33.0107250821060.1872-100000@tempest.blackhat.net>
On Wed, 25 Jul 2001, Nestor A. Marchesini wrote:
> HI Gnupic
>
> I try to compiling gpsim 0.20.9b and not get nothing errors, but when run the gpsim
> get this error.
>
> Gdk-ERROR **: file gdkfont.c: line 504 (gdk_car_width_wc): as assertion failed: (w
> ctomb(&c,character) == 1)
> aborting...
> Aborted (core dumped)
>
> I understanding what is a problem with the fonts in GUI, but...what is I should to install
> or reinstall?
>
> greeting... :)
Nestor,
The fix is probably within gpsim and not your system. Can you give me
a back trace of the crash:
1) Start gpsim in gdb (the GNU debugger).
$ gdb /usr/local/bin/gpsim
Your path to the gpsim executable may be different than this. However
by default the executable gets stored here. After entering this
command you'll have the gdb command line prompt.
2) Invoke gpsim from within the debugger. The options are the same as
those you would have typed had you invoked gpsim at the command line
prompt
(gdb) run -s yourcode.cod
gpsim should now be running. You should see the gpsim command line
prompt. So go ahead and run gpsim and do whatever it takes to crash
it! If there's a crash, gdb will take control and allow you to inspect
things.
gpsim> run
( crash )
When gpsim crashes you'll get the gdb command line prompt. Even if you
crashed in the bowels of some system library, it's possible to tell
where you last were inside gpsim by looking at the "backtrace" or bt:
(gdb) bt
This will printout something like this:
#0 0x00000072 in __strtol_internal (nptr=0x80cfb20 "E~\t@\210\004\b",
endptr=0x80d0430, base=0, group=0)
at eval.c:60
#1 0x400753db in P17C75x::create_sfr_map (this=0x80cfb20) at
p17c75x.cc:350
#2 0x40074d68 in P17C75x::create (this=0x80cfb20, ram_top=8191) at
p17c75x.cc:300
#3 0x40074c99 in P17C75x::construct () at p17c75x.cc:276
#4 0x4007b7d6 in add_processor (processor_type=0x80ad4a8 "p17c75x",
processor_new_name=0x0)
at pic-processor.cc:397
#5 0x40371a9e in cmd_processor::processor (this=0x40385c68,
processor_type=0x80ad4a8 "p17c75x",
processor_new_name=0x0) at cmd_processor.cc:167
<snip>
If you send me this printout, Ralf or I can pinpoint exactly where
gpsim made the erroneous call.
----------------
If gpsim is crashing before the command line prompt even shows, then
you can try this:
$ rm ~/.gpsim
This will remove the configuration file that gpsim creates. It
essentially records where all of the windows were the last time gpsim
ran. You can erase this history if it turns out that only one of the
gui windows is causing problems.
Regards,
Scott
