On Tue, 07 Nov 2000, Sven Neumann [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Raphael Quinet) writes:
I think that the best way to fix the screenshot plug-in is to add this
before the call to fork():
gimp_signal_private (SIGCHLD, SIG_DFL, SA_RESTART);
(don't forget to #include
On Mon, Nov 06, 2000 at 02:55:39PM +0100, Raphael Quinet [EMAIL PROTECTED] wrote:
helpbrowser.
Hmmm... Looks like we need a couple more beta releases before 1.2. ;-)
Simon and me are currently at the Systems'99, and, well, we probably need
a lot of couple of beta-releases ;) gimp seems to
Included below is a small test program that checks how the OS behaves
when a child process exits while the parent is blocking on waitpid()
and has a SIGCHLD handler installed (which also calls waitpid, and
thus could steal the status if the signal handler is called before
the first waitpid
On Sun, Nov 05, 2000 at 05:43:35PM -0500, thus said Garry R. Osgood:
Austin Donnelly wrote:
Is it generally known that mouse-down and waiting on brushes and
patterns pops up a larger preview window showing the whole
brush/pattern if it's larger than the preview?
Do many users
FreeBSD 3.4-STABLE:
installing signal handler...
forking...
waiting for child 25282 to exit...
child 25282 has exited
sig_pid = 25282
sig_status = 25600
main_pid = -1
main_status =
sigchld handler was called before waitpid (no status)
IRIX 6.5 IP22:
installing signal handler...
S/2 port have a look at
the __EMX__ part of the code in plug-in/common/gz.c? If possible,
after applying gimp-quinet-20001108-1.patch.gz that I uploaded to
ftp.gimp.org. That code looks very suspicious to me. It contains a
call to sleep(2) instead of using waitpid() for getting the output of
t
On 08 November, 2000 - Raphael Quinet sent me these 2.2K bytes:
If you are running another UNIX-like system (*BSD, HP-UX, AIX, etc.),
it would be nice if you could compile and run the following code and
report what it says. The code does not depend on glib, gtk or any
other libraries, so it
. I'll apply a modified version.
By the way, could someone who works on the OS/2 port have a look at
the __EMX__ part of the code in plug-in/common/gz.c? If possible,
after applying gimp-quinet-20001108-1.patch.gz that I uploaded to
ftp.gimp.org. That code looks very suspicious to me. It contains
±zÃh¤~¤£¹J¶Ü?
§A¤ß¤¤¦³¹Ú¶Ü?
³\§A¤@Ó¾Ö¦³°ªÁ~ªº¾÷·|
³\§A¤@Ó¹ê²{¹Ú·Qªº¾÷·|
Marc Lehmann wrote:
Simon and me are currently at the Systems'99, and, well, we probably need
a lot of couple of beta-releases ;) gimp seems to have a lot of small
problems like the selection going away after some time and not coming
back, refresh problems (a lot, but difficult to reproduce)
10 matches
Mail list logo
