[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#79228: marked as done (xlibs-static-dev: [libxf86dga] atexit functions don't work after XF86DGAGetVideo())



Your message dated Sat, 5 Mar 2011 23:32:37 +0100
with message-id <20110305223237.GA16523@debian.org>
and subject line Re: Bug#79228: atexit functions don't work after XF86DGAGetVideo
has caused the Debian Bug report #79228,
regarding xlibs-static-dev: [libxf86dga] atexit functions don't work after XF86DGAGetVideo()
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
79228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79228
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xlib6g-dev
Version: 3.3.6-11

This deals with the XFree86-DGA X extension's XF86DGAGetVideo function
in /hdb1/usr/X11R6/lib/libXxf86dga.a and functions set to run when the
program is exiting using atexit.

Any atexit function set up before a call to XF86DGAGetVideo will not run
on exit after the XF86DGAGetVideo call.  However, any functions set up
with atexit after the XF86DGAGetVideo call will run normally.  

If a program exits after XF86DGAGetVideo has been called it will print
the message "video memory protecting" at the end.  This happens
regardless of whether DGA mode was ever entered.  That message is
printed once even if XF86DGAGetVideo is called multiple times.  For an
atexit function to work in this case atexit must be used after the last
XF86DGAGetVideo call.

So basically, it seems that XF86DGAGetVideo installs some function using
the atexit mechanism.  Either that function causes an immediate exit or
it is installed in such a way that the list of functions to run at exit
is corrupted.  Clearly XF86DGAGetVideo is doing something wrong.  I
don't think it should even install a function to run at exit.  It would
be more logical for XF86DGADirectVideo to install such a function
because XF86DGAGetVideo just gets some information and
XF86DGADirectVideo actually starts DGA mode.

It is easy to investigate this behaviour.  Just get the source to the
XFree86-DGA demonstration client, add some function and put atexit calls
in various locations.  The demonstration client is /usr/X11R6/bin/dga in
package xbase-clients.

Oh, and BTW. my gcc package version is 2.95.2-13.  I don't think this is
compiler-related, but who knows.


--- End Message ---
--- Begin Message ---
Hi,

Boris Gjenero <bgjenero@sympatico.ca> (09/12/2000):
> This deals with the XFree86-DGA X extension's XF86DGAGetVideo
> function in /hdb1/usr/X11R6/lib/libXxf86dga.a and functions set to
> run when the program is exiting using atexit.
> 
> Any atexit function set up before a call to XF86DGAGetVideo will not
> run on exit after the XF86DGAGetVideo call.  However, any functions
> set up with atexit after the XF86DGAGetVideo call will run normally.
> […]

so, some years later, upstream declares DGA dead, so I could tag this
bug wontfix, or just close it. Let's do the latter.

KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: