| Server IP : 185.11.201.71 / Your IP : 192.168.7.18 Web Server : Apache/2.4.29 (Ubuntu) System : Linux tech-virtual-machine 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 User : tech ( 1000) PHP Version : 7.4.28 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/lintian/overrides/ |
Upload File : |
# The library calls exit() or abort() when a GL call is attempted that # it can't find a resolution for, which should only be in the case of # the caller not having the correct GL library dependencies present on # the system. At that point in execution, the only thing libepoxy # could do is return without calling down, but this means that the GL # operation wasn't executed, and you'll probably just get a segfault # later. For example, if we fail to resolve glGetString(), a common # early initialization command used by applications, they would need # an actual string. While you can imagine building code to support # failure from glGetString() resolution by returning a dummy string, # in the limit you'd end up building a GL implementation in the # process of trying to provide not-segfaulting-the-app fallback # behavior, and you'd never succeed anyway because no application # expects GL calls to error out, even with GL_OUT_OF_MEMORY. libepoxy0 binary: shlib-calls-exit