[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: incomplete warning message

From: Eric Blake
Subject: Re: incomplete warning message
Date: Mon, 30 Aug 2010 13:50:57 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100806 Fedora/3.1.2-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.2

On 05/31/2010 03:15 PM, Bruno Haible wrote:

Here's a case of an incomplete invocation stack trace in an autoconf warning:

   $ autoconf
   configure.ac:63: warning: gl_LIBUNISTRING_LIBSOURCE was called before 
   m4/libunistring-base.m4:21: gl_LIBUNISTRING_LIBSOURCE is expanded from...
   m4/gnulib-comp.m4:148: gl_INIT is expanded from...
   configure.ac:63: the top level
   configure.ac:63: warning: gl_LIBUNISTRING_LIBHEADER was called before 
   m4/libunistring-base.m4:53: gl_LIBUNISTRING_LIBHEADER is expanded from...

The last line looks like the stack trace would include at least one more line.
But it ends abruptly.

I'm wondering if somehow the mere act of printing the backtrace is deleting the stacktrace. I think this one should be easy enough to track down before 2.68, so I'm reviving it on my list of hot TODO items this week.

How to reproduce:
   $ wget http://www.haible.de/bruno/gnu/autoconf-bug-20100531.tar.gz
   $ tar xvfz autoconf-bug-20100531.tar.gz
   $ cd autoconf-bug-20100531
   $ autoconf

I saw it as well last week when cleaning up some gnulib AC_COMPILE_IFELSE usage patterns.

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]