From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Yao Qi <qiyaoltc@gmail.com>,
"Eli Zaretskii (eliz@gnu.org)" <eliz@gnu.org>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2 1/7] common: add scoped_fd
Date: Tue, 20 Feb 2018 10:46:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B236964A45F@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <CAH=s-PMaMfBHvK9YziOOzjZgY_r_XGb61-KQW-M_Go8=Gk3C1g@mail.gmail.com>
Hello Yao, Eli,
> > How about checking for mkstemp and, if not available, falling back to tmpnam.
>
> Can we unconditionally use tmpnam+open which are more portable? I know it is
> racy, but mkstemp is only used in a test case. It is overkill to me to do the configure
> check or import gnulib module.
>
> If we use mkstemp in gdb source (not test case) one day in the future, I prefer
> importing gnulib module. What do you think?
I'd rather not use tmpnam. This is really only a fallback for old systems.
I added mkstemp to update-gnulib.sh ...
---
diff --git a/gdb/gnulib/update-gnulib.sh b/gdb/gnulib/update-gnulib.sh
index 55cd6e0..d026536 100755
--- a/gdb/gnulib/update-gnulib.sh
+++ b/gdb/gnulib/update-gnulib.sh
@@ -59,6 +59,7 @@ IMPORTED_GNULIB_MODULES="\
update-copyright \
wchar \
wctype-h \
+ mkstemp \
"
# The gnulib commit ID to use for the update.
---
... cloned gnulib, updated my automake, ran that script, and ended up with:
# modified: gdb/gnulib/aclocal.m4
# modified: gdb/gnulib/config.in
# modified: gdb/gnulib/configure
# modified: gdb/gnulib/import/Makefile.am
# modified: gdb/gnulib/import/Makefile.in
# modified: gdb/gnulib/import/m4/gnulib-cache.m4
# modified: gdb/gnulib/import/m4/gnulib-comp.m4
# new file: gdb/gnulib/import/m4/mkstemp.m4
# new file: gdb/gnulib/import/m4/secure_getenv.m4
# new file: gdb/gnulib/import/m4/tempname.m4
# new file: gdb/gnulib/import/mkstemp.c
# new file: gdb/gnulib/import/secure_getenv.c
# new file: gdb/gnulib/import/tempname.c
# new file: gdb/gnulib/import/tempname.h
# modified: gdb/gnulib/update-gnulib.sh
If I did everything correctly, it looks like gnulib would only provide mkstemp as a fall-back. On
my system, it would still use the glibc version. Good. I wouldn't want to replace a standard
glibc function.
I have not tried building GDB with mingw cross tools, yet. Would you be able to test whether
this solves your build problem, Yao?
thanks,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2018-02-20 10:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 14:14 [PATCH v2 0/7] improve btrace enable error reporting Markus Metzger
2018-01-26 14:14 ` [PATCH v2 6/7] btrace: improve enable error messages Markus Metzger
2018-01-26 14:14 ` [PATCH v2 4/7] btrace, gdbserver: use exceptions to convey btrace enable/disable errors Markus Metzger
2018-01-26 14:14 ` [PATCH v2 2/7] common: add scoped_mmap Markus Metzger
2018-01-26 14:14 ` [PATCH v2 1/7] common: add scoped_fd Markus Metzger
2018-02-13 16:48 ` Yao Qi
2018-02-13 17:28 ` Metzger, Markus T
2018-02-14 15:22 ` Yao Qi
2018-02-14 17:26 ` Metzger, Markus T
2018-02-19 15:28 ` Metzger, Markus T
2018-02-20 10:12 ` Yao Qi
2018-02-20 10:46 ` Metzger, Markus T [this message]
2018-01-26 14:14 ` [PATCH v2 5/7] btrace, gdbserver: remove the to_supports_btrace target method Markus Metzger
2018-02-24 16:51 ` Maciej W. Rozycki
2018-02-26 13:08 ` Metzger, Markus T
2018-02-26 19:30 ` Andreas Arnez
2018-02-26 21:58 ` Maciej W. Rozycki
2018-02-27 10:57 ` Metzger, Markus T
2018-02-27 15:32 ` Maciej W. Rozycki
2018-02-27 18:14 ` Metzger, Markus T
2018-02-28 10:29 ` Maciej W. Rozycki
2018-02-28 11:09 ` Maciej W. Rozycki
2018-02-28 11:24 ` Metzger, Markus T
2018-02-28 12:53 ` Metzger, Markus T
2018-02-28 15:55 ` Maciej W. Rozycki
2018-02-28 16:08 ` Eli Zaretskii
2018-02-28 12:00 ` Yao Qi
2018-02-28 16:27 ` Sergio Durigan Junior
2018-03-01 11:33 ` Metzger, Markus T
2018-03-01 19:27 ` Sergio Durigan Junior
2018-03-05 12:14 ` Yao Qi
[not found] ` <87lgf64i24.fsf@redhat.com>
2018-03-06 9:02 ` Yao Qi
2018-03-06 16:32 ` Sergio Durigan Junior
2018-03-01 19:34 ` Maciej W. Rozycki
2018-01-26 14:14 ` [PATCH v2 3/7] btrace: prepare for throwing exceptions when enabling btrace Markus Metzger
2018-02-06 16:28 ` [PATCH v2 0/7] improve btrace enable error reporting Pedro Alves
2018-02-07 10:41 ` Metzger, Markus T
2018-02-07 12:11 ` Pedro Alves
2018-02-08 10:40 ` Metzger, Markus T
[not found] ` <9ce0c90a-5c71-0a7d-3779-f826369a95ec@redhat.com>
2018-02-08 13:49 ` Metzger, Markus T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A78C989F6D9628469189715575E55B236964A45F@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox