From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
jan.kratochvil@redhat.com, ralf.corsepius@rtems.org,
vapier@gentoo.org, joel.sherrill@oarcorp.com
Subject: Re: one week to gdb-7.6 release?
Date: Sun, 24 Mar 2013 00:01:00 -0000 [thread overview]
Message-ID: <20130323162534.GI5447@adacore.com> (raw)
In-Reply-To: <83ehf64cfs.fsf@gnu.org>
Hi Eli,
> Committed to the trunk as below. This incorporates comments from Jan.
> OK to commit the same to the 7.6 branch?
> 2013-03-18 Eli Zaretskii <eliz@gnu.org>
>
> * windows-nat.c (windows_get_absolute_argv0): New function.
> * windows-nat.h: Add its prototype.
>
> * main.c (get_init_files): Use filename_ncmp instead of strncmp.
> Use IS_DIR_SEPARATOR instead of looking for a character inside
> SLASH_STRING. Include filenames.h.
> (captured_main) [__MINGW32__]: Make argv[0] absolute, so that
> relocate_gdb_directory works when passed gdb_program_name.
> Include windows-nat.h.
I think that the patch, as is, breaks the windows-hosted cross-debugger
builds. windows-nat.o is only linked in when configured as a native
debugger:
if test "${gdb_native}" = "yes"; then
host_makefile_frag=${srcdir}/config/${gdb_host_cpu}/${gdb_host}.mh
I think that the standard approach in this case would be to define
a function in utils.h, and have its implementation in both posix-hdep.c
and mingw-hdep.c.
A minor nitpick on coding style: Can you add an empty line between
the comment documenting a function ands its definition?
Thank you,
--
Joel
next prev parent reply other threads:[~2013-03-23 16:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 16:09 Joel Brobecker
2013-03-20 16:14 ` Pedro Alves
2013-03-20 17:06 ` Jan Kratochvil
2013-03-20 17:08 ` Joel Sherrill
2013-03-20 17:20 ` Eli Zaretskii
2013-03-23 22:59 ` Eli Zaretskii
2013-03-24 0:01 ` Joel Brobecker [this message]
2013-03-24 0:07 ` Eli Zaretskii
2013-03-25 16:58 ` Joel Brobecker
2013-03-25 17:46 ` Eli Zaretskii
2013-03-25 18:10 ` Joel Brobecker
2013-03-29 8:02 ` Joel Brobecker
2013-03-29 14:03 ` Eli Zaretskii
2013-03-29 19:53 ` Joel Brobecker
2013-04-02 18:05 ` Eli Zaretskii
2013-04-05 13:03 ` Eli Zaretskii
2013-04-06 6:16 ` unbreak Windows hosted cross debugger builds (was: Re: one week to gdb-7.6 release?) Pedro Alves
2013-04-06 15:41 ` unbreak Windows hosted cross debugger builds " Eli Zaretskii
2013-03-29 15:23 ` one week to gdb-7.6 release? Ralf Corsepius
2013-03-29 16:42 ` m32r sim was " Joel Sherrill
2013-03-29 17:18 ` Mike Frysinger
2013-03-29 19:53 ` Joel Brobecker
2013-03-29 20:24 ` Joel Sherrill
2013-03-29 21:44 ` Joel Brobecker
2013-04-04 13:03 ` Ralf Corsepius
2013-04-10 15:01 ` Joel Brobecker
2013-03-25 19:08 ` Mark Kettenis
2013-03-25 19:12 ` Eli Zaretskii
2013-04-06 21:49 ` Pedro Alves
2013-04-07 3:58 ` Eli Zaretskii
2013-03-23 23:38 ` Joel Sherrill
2013-03-24 0:12 ` Mike Frysinger
2013-03-20 18:23 ` Ralf Corsepius
2013-04-01 19:56 ` Mike Frysinger
2013-03-29 12:53 Joel Sherrill
2013-03-29 14:15 ` Eli Zaretskii
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=20130323162534.GI5447@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=joel.sherrill@oarcorp.com \
--cc=palves@redhat.com \
--cc=ralf.corsepius@rtems.org \
--cc=vapier@gentoo.org \
/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