From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>, John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] [gdb/tetsuite] Add missing include in gdb.base/ctf-ptype.c
Date: Tue, 2 Apr 2024 16:23:35 +0200 [thread overview]
Message-ID: <1dd28397-74f4-4302-af4d-d7d0120093ed@suse.de> (raw)
In-Reply-To: <87bk6taxrj.fsf@tromey.com>
On 4/1/24 17:49, Tom Tromey wrote:
>>>>>> "John" == John Baldwin <jhb@FreeBSD.org> writes:
>
>>> int main ()
>>> {
>>> - /* Ensure that malloc is a pointer type; avoid use of "void" and any include files. */
>>> -/* extern char *malloc();*/
>>> -
>
> John> This certainly seems curious. Nothing in the commit log for when this was added
> John> gives any clue to why this comment is here, nor why the prototype is commented
> John> out. Other comments later in this function mention limitations of the linker on
> John> AIX, which makes me wonder how it was tested originally. Did you confirm that
> John> the test program compiled contained CTF but not DWARF when the test passed?
>
> This file was apparently just copy-pasted from ptype.c, which has this
> same commented-out line. It probably dates to the stabs days. I
> wouldn't worry too much about it... it could use a scrubbing and perhaps
> should be moved to gdb.ctf anyway.
OK, in that case ... pushed.
Thanks,
- Tom
prev parent reply other threads:[~2024-04-02 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 14:30 Tom de Vries
2024-03-27 14:30 ` [PATCH 2/3] [gdb/testsuite] Fix missing return type in gdb.linespec/break-asm-file.c Tom de Vries
2024-03-27 14:30 ` [PATCH 3/3] [gdb/testsuite] Add missing includes in gdb.trace/collection.c Tom de Vries
2024-03-28 17:21 ` [PATCH 1/3] [gdb/tetsuite] Add missing include in gdb.base/ctf-ptype.c John Baldwin
2024-03-29 10:39 ` Tom de Vries
2024-04-01 15:49 ` Tom Tromey
2024-04-02 14:23 ` Tom de Vries [this message]
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=1dd28397-74f4-4302-af4d-d7d0120093ed@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=tom@tromey.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