luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-09-22 10:16:14 +02:00
Code Issues Packages Projects Releases Wiki Activity
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
22,932 Commits 295 Branches 575 Tags 117 MiB
C 95.4%
Python 2.4%
Meson 1.3%
Objective-C 0.3%
Shell 0.2%
Other 0.4%
7ff0fb3af5
Go to file
Simon McVittie 7ff0fb3af5 spawn: Don't set a search path if we don't want to search PATH 
do_exec() and g_execute() rely on being passed a NULL search path
if we intend to avoid searching the PATH, but since the refactoring
in commit 62ce66d4, this was never done. This resulted in some spawn
calls searching the PATH when it was not intended.

Spawn calls that go through the posix_spawn fast-path were unaffected.

The deprecated gtester utility, as used in GTK 3, relies on the
ability to run an executable from the current working directory by
omitting the G_SPAWN_SEARCH_PATH flag. This *mostly* worked, because
our fallback PATH ends with ".". However, if an executable of the
same name existed in /usr/bin or /bin, it would run that instead of the
intended test: in particular, GTK 3's build-time tests failed if
ImageMagick happens to be installed, because gtester would accidentally
run display(1) instead of testsuite/gdk/display.

Fixes: 62ce66d4 "gspawn: Don’t use getenv() in async-signal-safe context"
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977961
2021-01-28 16:49:06 +00:00
.gitlab-ci ci: Fix msys-mingw32 CI builds due to package rename 2021-01-19 09:00:54 +00:00
docs gtestutils: Add g_test_get_path() API 2021-01-25 16:34:12 +01:00
fuzzing fuzzing: Add more parsing flags to the GKeyFile test 2020-12-17 12:42:54 +00:00
gio Merge branch 'fix/darwin-nosigpipe-regression' into 'master' 2021-01-27 07:35:04 +00:00
glib spawn: Don't set a search path if we don't want to search PATH 2021-01-28 16:49:06 +00:00
gmodule Fix g_module_symbol() under Windows sometimes not succeeding 2020-09-30 09:57:40 +02:00
gobject gtype: Improve formatting of GType documentation 2021-01-20 15:42:55 +00:00
gthread Meson: Override every dependency glib provides 2020-04-05 00:34:04 -04:00
m4macros m4macros: replace obsolete macros AC_TRY_RUN and AC_TRY_LINK in glib-2.0.m4 2021-01-25 16:13:08 -05:00
po Update Galician translation 2021-01-25 18:59:49 +00:00
subprojects Bump the libsysprof-capture dependency 2020-11-14 18:41:07 +00:00
tests Merge branch 'py-fixes' into 'master' 2020-11-20 18:10:40 +00:00
.clang-format CI: Code check formating in CI 2019-11-21 14:03:01 -06:00
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C 2012-07-30 04:09:08 -04:00
.gitattributes git: Add .gitattributes file with EOL settings for README.win32 2017-07-10 11:35:31 +01:00
.gitignore build: Drop autotools support 2019-01-15 15:11:43 +00:00
.gitlab-ci.yml ci: Temporarily fold SH and Py checks into style-check job 2020-11-20 14:48:14 +00:00
AUTHORS docs: Rename README.in to README.md for GitLab 2018-06-15 13:04:59 +01:00
check-abis.sh Correct shellcheck errors (and ignore world splitting when we want it) 2020-11-15 17:34:27 +01:00
clang-format-diff.py py: Reformat all Python files consistently 2020-11-17 15:50:07 +00:00
CONTRIBUTING.md docs: The mailing lists are no more 2019-07-23 11:05:17 +01:00
COPYING Update COPYING file to LGPLv2.1 2017-05-29 19:53:35 +02:00
glib-gettextize.in tree: Fix various typos and outdated terminology 2020-06-12 15:01:08 +01:00
glib.doap doap: Update the <mailing-list> element 2019-07-23 11:27:30 +01:00
glib.supp Merge branch 'settings-test-cleanups' into 'master' 2021-01-20 13:15:26 +00:00
HACKING docs: Update HACKING and README to mention Meson rather than autotools 2019-01-15 15:11:43 +00:00
INSTALL.in docs: Update INSTALL.in to mention Meson rather than autotools 2019-01-15 15:11:43 +00:00
meson_options.txt build: Add glib_debug option 2021-01-20 16:05:36 +01:00
meson.build Merge branch 'feature/glib-debug-build-option' into 'master' 2021-01-20 19:01:43 +00:00
msvc_recommended_pragmas.h Adding macros G_NORETURN and G_NORETURN_FUNCPTR 2020-11-25 11:34:05 +00:00
NEWS docs: Move ‘Notes’ section from README to NEWS 2021-01-13 13:58:57 +00:00
NEWS.pre-1-3 updates. 2001-04-03 19:22:44 +00:00
README docs: Rename README.in to README.md for GitLab 2018-06-15 13:04:59 +01:00
README.md docs: Move ‘Notes’ section from README to NEWS 2021-01-13 13:58:57 +00:00
README.rationale docs: Add a README.rationale documenting major design decisions 2014-05-04 18:22:09 +01:00
README.win32 README.win32: Update and convert to markdown 2019-08-27 12:57:32 +05:30
README.win32.md README.win32: Update and convert to markdown 2019-08-27 12:57:32 +05:30
template-tap.test.in tests: Remove redundant --tap options 2019-05-14 12:42:51 +01:00
template.test.in Meson: Install glib tests 2018-07-16 15:36:20 -04:00

README.md

GLib

GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.

The official download locations are: https://download.gnome.org/sources/glib

The official web site is: https://www.gtk.org/

Installation

See the file 'INSTALL.in'

How to report bugs

Bugs should be reported to the GNOME issue tracking system. (https://gitlab.gnome.org/GNOME/glib/issues/new). You will need to create an account for yourself.

In the bug report please include:

  • Information about your system. For instance:
    • What operating system and version
    • For Linux, what version of the C library
    • And anything else you think is relevant.
  • How to reproduce the bug.
    • If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
  • If the bug was a crash, the exact text that was printed out when the crash occurred.
  • Further information such as stack traces may be useful, but is not necessary.

Patches

Patches should also be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123): Closes: #123

Otherwise, create a new merge request that introduces the change, filing a separate issue is not required.