Re: Assertion error when building in Debug mode with MSVC
Paul Eggert <[email protected]> Tue, 25 Jan 2022 21:35:08 -0800
| Newsgroups | gmane.comp.lib.gnulib.bugs,gmane.comp.gnu.m4.bugs |
|---|---|
| Organization | UCLA Computer Science Department |
| Message-ID | <[email protected]> |
On 1/25/22 14:33, Julien Marrec wrote: >> Are the programs in question using the fclose module, either directly or > indirectly? > > Well, simply doing `m4.exe --version` does exhibit the issue. For the module info we need to look at something other than that. Does your m4 source code contain the files fclose.c and fclose.m4 somewhere? When you configured m4, did it say "checking whether fclose works on input streams" and if so what was the result? When you built m4, did the build compile fclose.c and create an object file fclose.o? > In close_stream, shouldn't the stdout FILE * be set to NULL if the close > worked No, as that's just a local variable so setting it to NULL won't persist until the next call.