From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 8.2 released!
Date: Sun, 09 Sep 2018 10:07:00 -0000 [thread overview]
Message-ID: <83ftyjq90h.fsf@gnu.org> (raw)
In-Reply-To: <announce.20180905091451.5DEB883A8F@joel.gnat.com> (message from Joel Brobecker on Wed, 5 Sep 2018 11:14:51 +0200 (CEST))
Building GDB 8.2 with MinGW GCC 7.3.0 on MS-Windows, I see a warning:
CXX record-btrace.o
In file included from exceptions.h:23:0,
from utils.h:24,
from defs.h:666,
from record-btrace.c:22:
ui-out.h: In function 'void btrace_insn_history(ui_out*, const btrace_thread_info*, const btrace_insn_iterator*, const btrace_insn_iterator*, gdb_disassembly_flags)':
ui-out.h:197:18: warning: 'asm_list.ui_out_emit_type<(ui_out_type)1>::m_uiout' may be used uninitialized in this function [-Wmaybe-uninitialized]
m_uiout->end (Type);
~~~~~~~~~~~~~^~~~~~
record-btrace.c:792:35: note: 'asm_list.ui_out_emit_type<(ui_out_type)1>::m_uiout' was declared here
gdb::optional<ui_out_emit_list> asm_list;
^~~~~~~~
Is this a real problem?
Also, a couple of places in remote-fileio.c use gettimeofday, which I
believe is deprecated under the recent versions of Posix; the
recommended replacement is clock_gettime.
Running the built GDB on itself produces the following warnings:
During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'.
During symbol reading, macro `WCHAR_MIN' redefined at d:/usr/include/wchar.h:70;
original definition at build-gnulib/import/stdint.h:561.
During symbol reading, macro `WCHAR_MAX' redefined at d:/usr/include/wchar.h:71;
original definition at build-gnulib/import/stdint.h:563.
Breakpoint 1 at 0x514740: file common/errors.c, line 51.
During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'.
During symbol reading, const value length mismatch for 'std::ratio<1, 1000000000>::num', got 8, expected 0.
During symbol reading, const value length mismatch for 'std::ratio<1, 1000000000>::den', got 8, expected 0.
During symbol reading, Member function "~_Sp_counted_base" (offset 0x3f07e1) is virtual but the vtable offset is not specified.
During symbol reading, cannot get low and high bounds for subprogram DIE at 0x40c43e.
During symbol reading, cannot get low and high bounds for subprogram DIE at 0x40c71b.
During symbol reading, Member function "~probe" (offset 0x438141) is virtual but the vtable offset is not specified.
During symbol reading, Child DIE 0x4433a0 and its abstract origin 0x448aff have different parents.
During symbol reading, Child DIE 0x44340f and its abstract origin 0x448aff have different parents.
During symbol reading, No DW_FORM_block* DW_AT_call_value for DW_TAG_call_site child DIE 0x447010 [in module D:\gnu\gdb-8.2\gdb\gdb.exe].
During symbol reading, No DW_FORM_block* DW_AT_call_value for DW_TAG_call_site child DIE 0x447050 [in module D:\gnu\gdb-8.2\gdb\gdb.exe].
During symbol reading, Multiple children of DIE 0x448d3a refer to DIE 0x448a80 as their abstract origin.
During symbol reading, Multiple children of DIE 0x448d78 refer to DIE 0x448a80 as their abstract origin.
During symbol reading, DIE 0x44aa21 and its abstract origin 0x446e69 have different tags.
During symbol reading, DIE 0x44b04f and its abstract origin 0x446e69 have different tags.
During symbol reading, Child DIE 0x44ffb5 and its abstract origin 0x44efe3 have different tags.
During symbol reading, Child DIE 0x4500cd and its abstract origin 0x448821 have different tags.
Anything here I should worry about?
Running "make -C gdb install-strip" fails:
/bin/sh /d/gnu/gdb-8.2/install-sh -c -s ./contrib/gdb-add-index.sh \
d:/usr/test-gdb-8.2/bin/$transformed_name.exe
d:\usr\bin\strip.exe:d:/usr/test-gdb-8.2/bin/_inst.8116_: file format not recognized
It fails because Makefile attempts to invoke 'strip' on a shell
script. I couldn't find any way to get past that except by hacking
gdb/Makefile to remove the offending portion, then installing that
shell script manually. How does this work on Posix hosts?
Thanks.
next parent reply other threads:[~2018-09-09 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20180905091451.5DEB883A8F@joel.gnat.com>
2018-09-09 10:07 ` Eli Zaretskii [this message]
2018-09-09 18:36 ` Tom Tromey
2018-09-09 19:24 ` Eli Zaretskii
2018-09-09 19:45 ` Tom Tromey
2018-09-09 19:49 ` Eli Zaretskii
2018-09-10 1:41 ` Tom Tromey
2018-09-10 7:16 ` Eli Zaretskii
2018-09-10 16:01 ` Tom Tromey
2018-09-10 17:29 ` Eli Zaretskii
2018-09-09 20:25 ` Mark Wielaard
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=83ftyjq90h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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