From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.bugs Subject: Re: `print' does not print Date: Sat, 23 Mar 2002 10:54:21 +0200 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: <1858-Sat23Mar2002105421+0200-eliz@is.elta.co.il> References: <200203202019.g2KKJfs4410490@jupiter.akutech-local.de> <2593-Fri22Mar2002121734+0200-eliz@is.elta.co.il> <15515.2661.133668.691007@jupiter.akutech-local.de> <3791-Fri22Mar2002135807+0200-eliz@is.elta.co.il> <15515.15905.64808.177966@jupiter.akutech-local.de> <2110-Fri22Mar2002190057+0200-eliz@is.elta.co.il> <15515.28200.228210.321561@jupiter.akutech-local.de> <1659-Fri22Mar2002203525+0200-eliz@is.elta.co.il> <15515.33581.247374.275450@jupiter.akutech-local.de> <1190-Fri22Mar2002221156+0200-eliz@is.elta.co.il> <15515.44484.750836.448899@jupiter.akutech-local.de> Reply-To: Eli Zaretskii NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1016874068 20396 127.0.0.1 (23 Mar 2002 09:01:08 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sat, 23 Mar 2002 09:01:08 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16ohOd-0005Ir-00 for ; Sat, 23 Mar 2002 10:01:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16ohOb-00052f-00; Sat, 23 Mar 2002 04:01:05 -0500 Original-Received: from mirapoint.inter.net.il ([192.114.186.20]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16ohLj-0004v1-00 for ; Sat, 23 Mar 2002 03:58:07 -0500 Original-Received: from zaretsky (diup-219-49.inter.net.il [213.8.219.49]) by mirapoint.inter.net.il (Mirapoint) with ESMTP id BGM26641; Sat, 23 Mar 2002 10:57:43 +0200 (IST) Original-To: ralf@akutech.de X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 In-Reply-To: <15515.44484.750836.448899@jupiter.akutech-local.de> (message from Ralf Fassel on Fri, 22 Mar 2002 23:18:44 +0100) Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:105 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:105 > Date: Fri, 22 Mar 2002 23:18:44 +0100 > From: Ralf Fassel > > So there _is_ a difference: cc fills the struct, gcc doesn't. Yes. The important part in the difference is that with cc, a new buffer is allocated to hold the buffered characters, while in the gcc build, _base stays at 0x0, i.e. the buffer wasn't allocated. (It is normal for buffered I/O routines to start with the buffer of teh FILE object unallocated, and only allocate it the first time any operation is requested for that FILE object.) > gcc: > > fwrite () at engine.c:601 > _wrtchk () at exportent.c:396 > ! setoserror () at aio.c:314 > _wrtchk () at exportent.c:383 > 383 exportent.c: No such file or directory. > fwrite () at engine.c:554 > printchar (ch=34, fun=273132596) at print.c:334 setoserror means there's some kind of error where it should have allocated the buffer (that's the _findbuf call in the cc build, I guess). Can you zero out errno before the call to fwrite, and see if it gets any value after fwrite returns? > Program received signal SIGTRAP, Trace/breakpoint trap. > > and I always get that SIGTRAP which restarts the fwrite again, but the > difference at ! is obvious. Probably a bug in GDB (SIGTRAP means that a breakpoint fired, but GDB didn't think there was a breakpoint at that place in the program). Anyway, this is a point where I'd strongly suggest compiling the library routines with enough debug info to be able to step through the library code and see what's wrong with Emacs. I guess in your case it's hard, since the library is proprietary, but the other report about the same behavior was for GNU/Linux, where we have glibc. Can someone please step through the glibc code in this case and see what's going on? _______________________________________________ Bug-gnu-emacs mailing list Bug-gnu-emacs@gnu.org http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs