From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6195 invoked by alias); 20 Jan 2003 17:06:42 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 6150 invoked from network); 20 Jan 2003 17:06:42 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 20 Jan 2003 17:06:42 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18ahGZ-0001Hu-00 for ; Mon, 20 Jan 2003 13:07:28 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18afNs-00071v-00 for ; Mon, 20 Jan 2003 12:06:52 -0500 Date: Mon, 20 Jan 2003 17:06:00 -0000 From: Daniel Jacobowitz To: overseers@sources.redhat.com Subject: [MAILER-DAEMON@sources.redhat.com: failure notice] Message-ID: <20030120170652.GA26995@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i X-SW-Source: 2003-q1/txt/msg00144.txt.bz2 Is the blacklisting acting up? According to DSBL, that IP has never been listed. ----- Forwarded message from MAILER-DAEMON@sources.redhat.com ----- Date: 20 Jan 2003 16:52:13 -0000 From: MAILER-DAEMON@sources.redhat.com Subject: failure notice To: drow@false.org Hi. This is the qmail-send program at sources.redhat.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : In an effort to cut down on our spam intake, we block email that is listed by certain open-relay tracking services. Unfortunately you may have just discovered the hard way that sometimes non-spam mail gets caught accidentally. In most cases you can clear this up by an upgrade to your mail server or sometimes by getting an erroneous listing removed. For more information about our use of these lists, see http://sources.redhat.com/lists.html#rbls The IP number that I am denying mail from is 65.125.64.184 The list that you are on is DSBL. See: http://dsbl.org/listing.php?ip=65.125.64.184 for more information about this list and why you are on it. If you are not actually a "spammer", you can add yourself to the sources.redhat.com "global allow list" by sending email *from*the*blocked*email*address* to: global-allow-subscribe-drow=false.org@sources.redhat.com This will enable you to send email without being subjected to further spam blocking. If you are actually a spammer then you should think long and hard about the people you are inconveniencing and come to the conclusion that what you are doing is both highly annoying and immoral. Contact binutils-owner@sources.redhat.com if you have questions about this. (#5.7.2) --- Below this line is a copy of the message. Return-Path: Received: (qmail 17551 invoked from network); 20 Jan 2003 16:52:12 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 20 Jan 2003 16:52:12 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18ah2X-0001GW-00 for ; Mon, 20 Jan 2003 12:52:58 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18af9q-0006yX-00 for ; Mon, 20 Jan 2003 11:52:22 -0500 Date: Mon, 20 Jan 2003 11:52:22 -0500 From: Daniel Jacobowitz To: binutils@sources.redhat.com Subject: Re: detect special mips64le dwarf2 line number length encoding Message-ID: <20030120165222.GA26733@nevyn.them.org> Mail-Followup-To: binutils@sources.redhat.com References: <20030119145937.GA15437@nevyn.them.org> <20030120052604.GA21412@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Mon, Jan 20, 2003 at 02:37:30PM -0200, Alexandre Oliva wrote: > On Jan 20, 2003, Daniel Jacobowitz wrote: > > > While I hate to dump more work on you, I would really rather we pursue > > this than propogate the nonstandard IRIX approach to this. I really > > don't think it would be much of a difficulty. > > Well, then, I can add this to my personal LINO to-do list, but I still > think the patch must go in, at the very least for compatibility with > mips64el binutils that have been out there for a while. This change > might look minor at first, but it actually fixes a linker crash, when > it tries to find out the line number associated with a given address, > to report a warning. Object files created using the current tools are > subject to this problem. Then, whenever we switch to the standard > format, everything will just keep on working, even in a > backward-compatible way. Nothing has ever used this non-standard format for little endian before; AFAIK only SGI used it, and after they'd dropped much of their little endian support. This only affects the mips64el-linux target as I understand it, since I thought that mips64el-elf would use the normal notation. So while I understand your point of view, "tools already out there" is a bit of a bunk, since the mips64el-linux target is brand new and has only been fully functional for a couple of weeks at best. It was contributed to GCC just days ago. I'm not going to fight you on this, and I understand you've got too much to do, and it's certainly good to prevent linker crashes even on bad input; but I really think your argument is bogus and that we should stop generating this form of debug info ASAP. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer ----- End forwarded message ----- -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer