From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Problem with library images on Windows (again) Date: Thu, 19 May 2005 10:13:23 +0200 Message-ID: References: <01c55c26$Blat.v2.4$0ef86680@zahav.net.il> Reply-To: Juanma Barranquero NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1116495955 26315 80.91.229.2 (19 May 2005 09:45:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 May 2005 09:45:55 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 19 11:45:52 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DYha2-0004h5-Qj for ged-emacs-devel@m.gmane.org; Thu, 19 May 2005 11:44:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DYhcW-0006Lf-T0 for ged-emacs-devel@m.gmane.org; Thu, 19 May 2005 05:47:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DYga5-0000ze-5N for emacs-devel@gnu.org; Thu, 19 May 2005 04:40:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DYgYN-0000am-8m for emacs-devel@gnu.org; Thu, 19 May 2005 04:38:51 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DYgWh-0007TE-WD for emacs-devel@gnu.org; Thu, 19 May 2005 04:37:08 -0400 Original-Received: from [64.233.184.200] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DYgHu-0007Qw-Pe for emacs-devel@gnu.org; Thu, 19 May 2005 04:21:50 -0400 Original-Received: by wproxy.gmail.com with SMTP id 50so604173wri for ; Thu, 19 May 2005 01:13:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qGyUyr1mvmTDqtz/Irml7uO8UWB3Oivt27cgNqNlfVAe3LBVlHlhYBB1qoSN1Y1IsaEH4AYJ99JxwII7jsaMMi7GGthV4+X618i9G0yJJ0GU4gR1Em80OuVl6u340DS2iTL0i9SztoHTL7KWLySTPf921gT4AewFEDz5REwv1u8= Original-Received: by 10.54.33.53 with SMTP id g53mr942691wrg; Thu, 19 May 2005 01:13:23 -0700 (PDT) Original-Received: by 10.54.82.6 with HTTP; Thu, 19 May 2005 01:13:23 -0700 (PDT) Original-To: emacs-devel@gnu.org In-Reply-To: <01c55c26$Blat.v2.4$0ef86680@zahav.net.il> Content-Disposition: inline X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:37342 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37342 On 5/19/05, Eli Zaretskii wrote: > Can you set a watchpoint on the address where EBX is saved on the > stack, and then see what code clobbers that value? Yes. tiff_load pushes EBX into the stack, and then goes around happily pushing arguments and calling functions from the TIFF library, which apparently don't remove their arguments from the stack (nor does it the tiff_load code). So the stack keeps growing and, by the time tiff_load does the POP EBX, it gets random garbage. On returning from tiff_load the frame pointer is restored, so the spurious stack data is just discarded. So it seems like a mismatch between the calling convention used to implement the TIFF library and the one MSVC thinks the TIFF functions are using. I'll dig around a little more. But any help is much appreciated. --=20 /L/e/k/t/u