Login or Register to Ask a Question and Join Our Community


Programming

Xlib Problem: XCloseDisplay seg fault

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Programming Xlib Problem: XCloseDisplay seg fault
# 1  
Old 09-04-2008
Data Xlib Problem: XCloseDisplay seg fault
Hi,
First of all forgive me if Xlib related problems does not go under this thread.

In my main program, im using Xlib`s XImage type object which contains a regularly updating bitmap, and maps the XImage to a Xwindow using XPutImage.
( XCreateImage is used to create the XImage. )

The program also have another thread as the X-Event handler. there at an expose event, XPutImage is used to update the XWindow.

The XLib functions works fine and does the job, but the problems occurs when tried to exit the main, before exiting im calling the following functions in order to release the X-System resources taken.
Code:
	/* Destroy the XImage - de alloc memory */
	XDestroyImage( xImage );

	/* destroy specified window */
	XDestroyWindow( pDisplay, showWindow );
		
	/* disconnect from X server */
	XCloseDisplay( pDisplay );    -------> give a segmentation fault

When @ the XCloseDisplay( pDisplay ); function call it gives a segmentation fault.
I tried different solutions but never went right. can anybody have any comments on what im doing wrong here.
Thankx.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Debian

Linux, Debian - Segmentation Fault problem.

Hi guys, first of all apologize for my English... I have a big problem with "Segmentation fault", when running my game server. Console: (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x00007ffff702aca4 in std::basic_ostream<char,... (1 Reply)
Discussion started by: Arson.
1 Replies

2. Shell Programming and Scripting

Find and split the list of files with suffiz of seg**

Hi,. I am writing a script to get the new files and split them. Requirement Find the new files under the path "/wload/scmp/app/data/OAS" (There are 5 sub folders). Gunzip the files which are having .gz suffix. Put the list of files in the filename in the format... (0 Replies)
Discussion started by: Satish Shettar
0 Replies

3. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this : i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies

4. Programming

'seg' assembly instruction in .s file

Is this x86? I encountered this instruction and can't seem to find any info on what it does anywhere. Any ideas? This is how it appears: seg es (4 Replies)
Discussion started by: stevenswj
4 Replies

5. Programming

Seg Fault Running AIX COBOL program

Hi some help read............ I'm getting a segmentation fault when I run an AIX COBOL/Db2 program. I initiate the program from the command line, but it hangs, and then when I press enter it generates a segmantation fault and produces a core dump. The box is running AIX software level ... (5 Replies)
Discussion started by: steve_f
5 Replies

6. HP-UX

HP-UX 64 compilation causing some code to seg fault

Hello everyone, Today we are attempting to port some legacy C code to a 64 HP-UX machine at my company and there is kind of a strange error we ran into. there is a small function they have defined called zgetenv that accepts a char* and basically just does some null checking and returns ... (0 Replies)
Discussion started by: khadesh
0 Replies

7. Programming

Open Suse 10 seg fault

Okay, so here is some code that when compiled on Fedora Core 6 works great, but when I compile and run it on OpenSuse 10 it gives back a seg fault when trying to join the 2nd thead. #include <pthread.h> #include <stdio.h> int print_message_function( void *ptr ); int x = 1; main() { ... (1 Reply)
Discussion started by: chrisdrobison
1 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

xlockdisplay

XInitThreads(3) 						  XLIB FUNCTIONS						   XInitThreads(3)

NAME

       XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support

SYNTAX

       Status XInitThreads(void);

       void XLockDisplay(Display *display);

       void XUnlockDisplay(Display *display);

ARGUMENTS

       display	 Specifies the connection to the X server.

DESCRIPTION

       The XInitThreads function initializes Xlib support for concurrent threads.  This function must be the first Xlib function a multi-threaded
       program calls, and it must complete before any other Xlib call is made.	This function returns a nonzero status if initialization was suc-
       cessful; otherwise, it returns zero.  On systems that do not support threads, this function always returns zero.

       It is only necessary to call this function if multiple threads might use Xlib concurrently.  If all calls to Xlib functions are protected
       by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini-
       tialization is not required.  It is recommended that single-threaded programs not call this function.

       The XLockDisplay function locks out all other threads from using the specified display.	Other threads attempting to use the display will
       block until the display is unlocked by this thread.  Nested calls to XLockDisplay work correctly; the display will not actually be unlocked
       until XUnlockDisplay has been called the same number of times as XLockDisplay.  This function has no effect unless Xlib was successfully
       initialized for threads using XInitThreads.

       The XUnlockDisplay function allows other threads to use the specified display again.  Any threads that have blocked on the display are
       allowed to continue.  Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must
       be called an equal number of times before the display is actually unlocked.  This function has no effect unless Xlib was successfully ini-
       tialized for threads using XInitThreads.

SEE ALSO

       Xlib - C Language X Interface

X Version 11							   libX11 1.5.0 						   XInitThreads(3)