469,963 Members | 1,806 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,963 developers. It's quick & easy.

Fatal Error in C

Hi,

I am writing a program in C. The following error message appears:

************************************************** ************************
"XIO: fatal IO error 14 (Bad address) on X server ":0.0"after 0
requests (0 known processed) with 0 events remaining. Segmentation
fault."
************************************************** ************************

I am using linux - Gnome Desktop version 2.10.2 and run my program in
the terminal.

Do you know what is going on?

Many thanks,
Kenneth

May 22 '06 #1
6 7321
ke********@yahoo.com.hk wrote:
Hi,

I am writing a program in C. The following error message appears:

************************************************* *************************
"XIO: fatal IO error 14 (Bad address) on X server ":0.0"after 0
requests (0 known processed) with 0 events remaining. Segmentation
fault."
************************************************* *************************

I am using linux - Gnome Desktop version 2.10.2 and run my program in
the terminal.

Do you know what is going on?

Many thanks,
Kenneth


<OT>
Quick! Before the first reply comes. Ok, I have my soda, popcorn, and
a comfortable seat. Let the show begin! ;)
</OT>
May 22 '06 #2
ke********@yahoo.com.hk said:
Hi,

I am writing a program in C. The following error message appears:

************************************************** ************************
"XIO: fatal IO error 14 (Bad address) on X server ":0.0"after 0
requests (0 known processed) with 0 events remaining. Segmentation
fault."
************************************************** ************************

I am using linux - Gnome Desktop version 2.10.2 and run my program in
the terminal.

Do you know what is going on?


Yes.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)
May 22 '06 #3
Actually it is a opengl program using C. and my program and the
animation are running properly. Suddenly it happens.

So, what is going on?

May 22 '06 #4
Ico
ke********@yahoo.com.hk wrote:
Hi,

I am writing a program in C. The following error message appears:

************************************************** ************************
"XIO: fatal IO error 14 (Bad address) on X server ":0.0"after 0
requests (0 known processed) with 0 events remaining. Segmentation
fault."
************************************************** ************************

I am using linux - Gnome Desktop version 2.10.2 and run my program in
the terminal.

Do you know what is going on?


[Offtopic] Don't mix threads and X. For more info, go to comp.windows.x.

--
:wq
^X^Cy^K^X^C^C^C^C
May 22 '06 #5

"Ico" <us****@zevv.nl> wrote in message
news:44**********************@dreader30.news.xs4al l.nl...
ke********@yahoo.com.hk wrote:
Hi,

I am writing a program in C. The following error message appears:

************************************************** ************************
"XIO: fatal IO error 14 (Bad address) on X server ":0.0"after 0
requests (0 known processed) with 0 events remaining. Segmentation
fault."
************************************************** ************************

I am using linux - Gnome Desktop version 2.10.2 and run my program in
the terminal.

Do you know what is going on?


[Offtopic] Don't mix threads and X. For more info, go to comp.windows.x.


Don't let these guys discourage you. As long as you use an OS written in C,
then I'll pretend to know what a segfault is. joe
May 22 '06 #6
ke********@yahoo.com.hk opined:
Actually it is a opengl program using C. and my program and the
animation are running properly. Suddenly it happens.

So, what is going on?


To Roberto Waltman: Crack open the soda. It begins... NOW!

To OP:

Quote context, even yourself. Read the link in my sig -- carefully.

So, what IS going on, then?

Well, my crystal ball (lovingly designed by DS9K, and delivered by a
bunch of flying pigs out of somebody else's UB ridden code) tells me
that you have a memory leak, and that the root cause is on the line
42. Apart from that, there's 17 other instances of Undefined
Behaviour, and 57 `printf()` statements not terminated by '\n'. The
latter are preventing you to see the problem clearly, as there's
actually no output (apart from the error message).

Now, if you want any help, please post a minimal compilable example of
your code, and make sure that the problem is not OS, processor or
compiler extension specific. If any of the previous do not hold, you
should go where the offending one(s) are topical. Here, we discuss
only Standard C, and it knows not of threads, X windows, Y windows, or
even MS Windows.

--
Insults are effective only where emotion is present.
-- Spock, "Who Mourns for Adonais?" stardate 3468.1

<http://clc-wiki.net/wiki/Introduction_to_comp.lang.c>

May 22 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by PeterF | last post: by
8 posts views Thread by Tim Tyler | last post: by
6 posts views Thread by Steve Crawford | last post: by
1 post views Thread by rainxy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.