Qt3 and XFree86 4.2: Fatal IO error

QNX Newsgroups (Archives) openqnx.developer
1

Hi

I am using XFree86 4.2 and Qt3 from sourgeforge and I am getting occasional:
“fatal IO error: client killed” from my Qt application. It seems to happen
when I am displaying bitmaps (QLabel pixmap) in my application. It only
happens very rarely (one out of ~100 times).

I looked into the Qt source and found that the above error is outputted from
the X fatal IO error handle (setup with XSetIOErrorHandler()).

Any ideas?

It does not seem to happen under XPhoton, so I might have to go back to
XPhoton if I can’t figure this out.

Thanks
Jens

2

I usually see “client killed” message when I ran out of memory.
maybe you are short of that?

frank

On Mon, 6 May 2002 JHJ=UiaQT4aTYH8AvxtiuMwx3w@public.gmane.org wrote:

Hi

I am using XFree86 4.2 and Qt3 from sourgeforge and I am getting occasional:
“fatal IO error: client killed” from my Qt application. It seems to happen
when I am displaying bitmaps (QLabel pixmap) in my application. It only
happens very rarely (one out of ~100 times).

I looked into the Qt source and found that the above error is outputted from
the X fatal IO error handle (setup with XSetIOErrorHandler()).

Any ideas?

It does not seem to happen under XPhoton, so I might have to go back to
XPhoton if I can’t figure this out.

Thanks
Jens

3

Hi Frank

Thanks for the suggestion - but it does not seem to be a memory problem as I
got 70 MB free (reported by “pidin info”) when it happens.

I also realized that it does not seem to be related to bitmap displaying -
it also happens with other dialogs. The program gets killed when
QDialog::exec() is called.

Jens

-----Original Message-----
From: Frank Liu [mailto:liug=wJsaexb6DEQ3G7qi5jAxu4dd74u8MsAO@public.gmane.org]
Sent: Monday, May 06, 2002 5:54 PM
To: JHJ=UiaQT4aTYH8AvxtiuMwx3w@public.gmane.org
Cc: openqnx-developer=5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Openqnx-developer] Qt3 and XFree86 4.2: Fatal IO error



I usually see “client killed” message when I ran out of memory.
maybe you are short of that?

frank

On Mon, 6 May 2002 JHJ=UiaQT4aTYH8AvxtiuMwx3w@public.gmane.org wrote:

Hi

I am using XFree86 4.2 and Qt3 from sourgeforge and I am getting
occasional:
“fatal IO error: client killed” from my Qt application. It seems to happen
when I am displaying bitmaps (QLabel pixmap) in my application. It only
happens very rarely (one out of ~100 times).

I looked into the Qt source and found that the above error is outputted
from
the X fatal IO error handle (setup with XSetIOErrorHandler()).

Any ideas?

It does not seem to happen under XPhoton, so I might have to go back to
XPhoton if I can’t figure this out.

Thanks
Jens

4

Jens and I had some private emails on this issue.
We found the problem only exists in 6.1, and the same program
works fine in 6.2beta. Apparently, something in 6.2beta fixed it.

Frank

On Tue, 7 May 2002 JHJ=UiaQT4aTYH8AvxtiuMwx3w@public.gmane.org wrote:

Hi Frank

Thanks for the suggestion - but it does not seem to be a memory problem as I
got 70 MB free (reported by “pidin info”) when it happens.

I also realized that it does not seem to be related to bitmap displaying -
it also happens with other dialogs. The program gets killed when
QDialog::exec() is called.

Jens

-----Original Message-----
From: Frank Liu [mailto:liug=> wJsaexb6DEQ3G7qi5jAxu4dd74u8MsAO@public.gmane.org> ]
Sent: Monday, May 06, 2002 5:54 PM
To: JHJ=> UiaQT4aTYH8AvxtiuMwx3w@public.gmane.org
Cc: openqnx-developer=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Openqnx-developer] Qt3 and XFree86 4.2: Fatal IO error



I usually see “client killed” message when I ran out of memory.
maybe you are short of that?

frank

On Mon, 6 May 2002 JHJ=> UiaQT4aTYH8AvxtiuMwx3w@public.gmane.org > wrote:

Hi

I am using XFree86 4.2 and Qt3 from sourgeforge and I am getting
occasional:
“fatal IO error: client killed” from my Qt application. It seems to happen
when I am displaying bitmaps (QLabel pixmap) in my application. It only
happens very rarely (one out of ~100 times).

I looked into the Qt source and found that the above error is outputted
from
the X fatal IO error handle (setup with XSetIOErrorHandler()).

Any ideas?

It does not seem to happen under XPhoton, so I might have to go back to
XPhoton if I can’t figure this out.

Thanks
Jens