On Sun, Dec 26, 1999 at 06:31:10AM +0900, SHIRASAKI Yasuhiro
<[EMAIL PROTECTED]> wrote:
> Should we remove _() from there?
The right thing is to remove superfluous code when it makes problems ;)
--
-==- |
==-- _
>>#4 0x810b5c0 in on_signal (sig_num=11) at main.c:471
>Signal 11 is a segfault (what Windows would have called an Access
>Violation, or GPF). We should fix that segfault...
Yes, I know that. The problem is that segfault happens in the
signal handler for segfault itself. _() for segfault message
On Sun, Dec 26, 1999 at 06:31:10AM +0900, SHIRASAKI Yasuhiro wrote:
>#4 0x810b5c0 in on_signal (sig_num=11) at main.c:471
Signal 11 is a segfault (what Windows would have called an Access
Violation, or GPF). We should fix that segfault...
/* Steinar */
--
Homepage: http://members.xoom.com/snee
Hi,
_() in the gimp signal handler sometimes caused infinite loop:
#0 0x2836ae7a in dcgettext__ () from /usr/local/lib/libintl.so.1
#1 0x2836b73d in dgettext__ () from /usr/local/lib/libintl.so.1
#2 0x2836b75e in gettext__ () from /usr/local/lib/libintl.so.1
#3 0x2836aca4 in gettext () from
