public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Clifton <nickc@cygnus.com>, Richard Earnshaw <rearnsha@arm.com>
Cc: GDB Patches <gdb-patches@sourceware.cygnus.com>,
	SID Discussion <sid@sources.redhat.com>
Subject: dejagnu hang from target.exp (prune_warnings)
Date: Thu, 18 Jan 2001 23:50:00 -0000	[thread overview]
Message-ID: <3A67F120.30D17FF6@cygnus.com> (raw)

The change:

< 2001-01-12  Richard Earnshaw  <rearnsha@arm.com>
< 
<       * target.exp (prune_warnings): Prune warnings from NetBSD
linker.
< 

checked in by NickC causes dejagnu to hang (or to at least take a very
very very very very long walk) when the compiler generates lots of
output.  Looking at the patch:

-     # Or the NetBSD ones.
-     regsub -all "(^|\n)(.*:\[0-9\]+: warning: \[^\n\]* possibly used
unsafely, use \[^\n\]*\n?)" $text "\\1" text
-     regsub -all "(^|\n)(.*: warning: reference to compatibility
glob\[^\n\]*\n?)" $text "\\1" text

that leading ``.*'' is just too generous :-(

The attatched stops the problem for me.  Can someone please confirm this
doesn't break on NetBSD.

	enjoy,
		Andrew
Fri Jan 19 18:37:19 2001  Andrew Cagney  <cagney@b1.cygnus.com>

	* lib/target.exp (prune_warnings): Avoid ``.*'' in NetBSD warnings
 	pattern.

Index: lib/target.exp
===================================================================
RCS file: /cvs/src/src/dejagnu/lib/target.exp,v
retrieving revision 1.7
diff -p -r1.7 target.exp
*** target.exp	2001/01/12 18:13:40	1.7
--- target.exp	2001/01/19 07:39:47
*************** proc prune_warnings { text } {
*** 262,269 ****
      regsub -all "(^|\n)(ld(|32|64): Giving up.*Use -wall\[^\n\]*\n?)+" $text "\\1" text
  
      # Or the NetBSD ones.
!     regsub -all "(^|\n)(.*:\[0-9\]+: warning: \[^\n\]* possibly used unsafely, use \[^\n\]*\n?)" $text "\\1" text
!     regsub -all "(^|\n)(.*: warning: reference to compatibility glob\[^\n\]*\n?)" $text "\\1" text
  
      # GNU ld warns about functions marked as dangerous in GNU libc.
      regsub -all "(^|\n)\[^\n\]*: In function\[^\n\]*\n\[^\n\]\[^\n\]*function is dangerous\[^\n\]*" $text "" text
--- 262,269 ----
      regsub -all "(^|\n)(ld(|32|64): Giving up.*Use -wall\[^\n\]*\n?)+" $text "\\1" text
  
      # Or the NetBSD ones.
!     regsub -all "(^|\n)(\[^\n\]*:\[0-9\]+: warning: \[^\n\]* possibly used unsafely, use \[^\n\]*\n?)" $text "\\1" text
!     regsub -all "(^|\n)(\[^\n\]*: warning: reference to compatibility glob\[^\n\]*\n?)" $text "\\1" text
  
      # GNU ld warns about functions marked as dangerous in GNU libc.
      regsub -all "(^|\n)\[^\n\]*: In function\[^\n\]*\n\[^\n\]\[^\n\]*function is dangerous\[^\n\]*" $text "" text

             reply	other threads:[~2001-01-18 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18 23:50 Andrew Cagney [this message]
2001-01-19  6:59 ` Richard Earnshaw
2001-01-19 14:54   ` Andrew Cagney

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=3A67F120.30D17FF6@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=nickc@cygnus.com \
    --cc=rearnsha@arm.com \
    --cc=sid@sources.redhat.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).