[Bug 240761] Segmentation fault in OpenCL programs using clover

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240761

            Bug ID: 240761
           Summary: Segmentation fault in OpenCL programs using clover
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
          Assignee: [email protected]
             Flags: maintainer-feedback?([email protected])
 Attachment #207731 text/plain
         mime type:

Created attachment 207731
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207731&action=edit
Constructor/destructor workaround

Hello. This is a long standing bug (at least for me), but I've decided to
report only now. When you use an OpenCL program using lang/clover, the programm
will crash at exit.

I've tracked the problem to a file src/util/u_queue.c in mesa sources. The
segmentation fault occurs while executing atexit handlers (one such hander is
added in global_init() ). BTW, there is nothing wrong with atexit_handler()
function itself: it can be empty and the result will be the same (segmentation
fault).

I tried to reproduce this behavior in a test program without success, so I have
no idea what is causing the bug.

Meanwhile, I wrote a little workarond using constructor and destructor
functions (supported by both clang and gcc). This works just fine without any
errors.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.