From: Sam James <sam@gentoo.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Peter Frazier <mrpeterfrazier@gmail.com>, bug-gnulib@gnu.org
Subject: Re: coreutils/gnulib - fts.c dangling pointers & gcc 13.1
Date: Sat, 4 Feb 2023 16:14:14 +0000 [thread overview]
Message-ID: <7B6A1D32-7ECD-4DE0-9E0C-1955F9B756B5@gentoo.org> (raw)
In-Reply-To: <f073d35b-8b49-c67e-ff47-d245aefdf2b7@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
> On 3 Feb 2023, at 22:11, Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> On 2023-02-03 12:24, Peter Frazier wrote:
>> dangling pointers & gcc 13.1
>> problem with:
>> coreutils/gnulib, fts.c
>> compilation failure:
>> -Werror=use-after-free error
>> approach to resolution (thus far):
>> post free of vars, I set the vars to NULL, but it did not help
>
> Could you be more specific about the symptoms you observed, and how to reproduce them? For one thing, GCC 13.1 has not been released yet, as far as I can see.
>
Yes, we need the full build log, and the commands run to obtain them. GCC 13 has not yet been
released so we need the 'gcc -v' output too.
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2023-02-04 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 20:24 coreutils/gnulib - fts.c dangling pointers & gcc 13.1 Peter Frazier
2023-02-03 22:11 ` Paul Eggert
2023-02-04 16:14 ` Sam James [this message]
2023-02-04 18:46 ` Paul Eggert
2023-02-04 19:53 ` Sam James
2023-02-04 20:20 ` Paul Eggert
2023-02-04 20:23 ` Sam James
2023-02-04 22:03 ` Paul Eggert
2023-02-04 22:10 ` Sam James
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7B6A1D32-7ECD-4DE0-9E0C-1955F9B756B5@gentoo.org \
--to=sam@gentoo.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=mrpeterfrazier@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).