From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.bugs Subject: bug#47067: 28.0.50; [feature/native-comp] Crash while scrolling through dispnew.c Date: Sat, 13 Mar 2021 15:45:52 +0000 Message-ID: References: <83sg52lykn.fsf@gnu.org> <83mtv8lrmf.fsf@gnu.org> <83czw4lelg.fsf@gnu.org> <83mtv8jgn2.fsf@gnu.org> <834khfjv7q.fsf@gnu.org> <83tupfia1m.fsf@gnu.org> <83mtv7hy5c.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30858"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Andrea Corallo , 47067@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Mar 13 16:47:30 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lL6UC-0007tA-DV for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Mar 2021 16:47:28 +0100 Original-Received: from localhost ([::1]:57560 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lL6UB-0004K2-Fx for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Mar 2021 10:47:27 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53638) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lL6Tm-0004Jw-Aw for bug-gnu-emacs@gnu.org; Sat, 13 Mar 2021 10:47:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48951) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lL6Tm-000769-3B for bug-gnu-emacs@gnu.org; Sat, 13 Mar 2021 10:47:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lL6Tm-0000fS-0B for bug-gnu-emacs@gnu.org; Sat, 13 Mar 2021 10:47:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 13 Mar 2021 15:47:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47067 X-GNU-PR-Package: emacs Original-Received: via spool by 47067-submit@debbugs.gnu.org id=B47067.16156503972534 (code B ref 47067); Sat, 13 Mar 2021 15:47:01 +0000 Original-Received: (at 47067) by debbugs.gnu.org; 13 Mar 2021 15:46:37 +0000 Original-Received: from localhost ([127.0.0.1]:60497 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lL6TN-0000en-8q for submit@debbugs.gnu.org; Sat, 13 Mar 2021 10:46:37 -0500 Original-Received: from mail-oi1-f178.google.com ([209.85.167.178]:43876) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lL6TK-0000ea-MA for 47067@debbugs.gnu.org; Sat, 13 Mar 2021 10:46:35 -0500 Original-Received: by mail-oi1-f178.google.com with SMTP id d20so30059624oiw.10 for <47067@debbugs.gnu.org>; Sat, 13 Mar 2021 07:46:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6tWnFVvkM7TUpx2yIYKXVn17s7k1h1aHurecadET5+Q=; b=LKpMVcPBAEaqMcqmHNhZwRd6F82NIYT6On7j89Kdr/YcsPqfGsAOJ73skKFLoQX9OP Ri//o2l7O0lXFndh8BRzZdD50Iu6gTw/QdoJRzaYi1QuOFErU9hqf8D4tFCWkZfndd5x 2B9E8Sh3fS0qfVvxZSkHa+vVuuuI/W0DHJITT1MPhwNzoDZ/bIKVVfilmj5mOIZ66TuE YVoGnjo4dW/b1qWkwIqo+TstWxNNsXtMBd8zIiphyJcJn66CDYIcgIf2eW7sXao5Ggwb KiPK4P3GkkSlpr9/s3a6xdVe3k0odJaQUdmKNanWDzHr9zbh+8ovcvPIUezBPMEHi81k k8hQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6tWnFVvkM7TUpx2yIYKXVn17s7k1h1aHurecadET5+Q=; b=CusaOYsUBopgGhFTh1Astxdow2v5nzbSr4rPgUvuIbigsRnBNZcnwD5IgF3IfF37xQ IhwC/5cNtVXXqblAoqNSl4FY6MVaKHhb0OD8HasvhCZIj1QIiHRl2oC8+1ubjt/aiING 38jGuKPvL6frSq+YZOUB3iZxTtMKgLd209kXnE3zuvfAL2zmKrJTdahg8/BnFJXSPfzM 3BWOHrOco1VRPwZ30tlbzuC9WhOhj5BNnO0rsfMfITr9H65XrrEykZBhhSAjpTeCRa+8 d65oyLIh84PVGyqYdJfrWIq9C7kTzuZikP8IK3tWjppXmxOEcTqk2vGYa+39Chp7ckMm GylA== X-Gm-Message-State: AOAM533gR5NXYNe8zppRG8HzrUeQsTMic7x3WobM9D5cIc5wEGla0H5c 1NZegkcSCd03liT5856XDPF5FWa5NsB9RPAawi8= X-Google-Smtp-Source: ABdhPJzJGUaQLfIMiX11x0oJRqFTkPVGyToB0fCYeoW2b2J49aCelmWNTjR4HOMqXmYF3VEuGNADaFrF9TJeUO3j/K8= X-Received: by 2002:a54:4196:: with SMTP id 22mr12934421oiy.30.1615650388835; Sat, 13 Mar 2021 07:46:28 -0800 (PST) In-Reply-To: <83mtv7hy5c.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:202267 Archived-At: On Sat, Mar 13, 2021 at 3:27 PM Eli Zaretskii wrote: > > > It's nowhere in the C backtrace, only its caller > > > > But it was in one of the previous backtraces? > > Too many moons ago. The ABI was bumped since then, and so did the > *.eln files. The code you pasted matches c-beginning-of-statement-1, and so does the Lisp backtrace, so I would suggest we go with it... > > > > Can you disassemble the function around 0x09c32285 (or, in another > > > > dump, whatever calls Flss), particularly the 256 bytes or so before > > > > that EIP? > > > > > > Below. The updated address for the caller of Flss is 0x09d82285, > > > which is not in any function whose name is known to GDB. > > > > That's normal, assuming you didn't compile with comp-debug > 0. > > If that's normal, why did Andrea say that he didn't see such "??" in > his backtraces? And if that's because Andrea builds with comp-debug > above the default zero, then I think either the doc string or the set > of values (or both) need to be updated: > > (defcustom comp-debug 0 > "Debug level for native compilation, a number between 0 and 3. > This is intended for debugging the compiler itself. > 0 no debugging output. > This is the recommended value unless you are debugging the compiler itself. > 1 emit debug symbols and dump pseudo C code. > 2 dump gcc passes and libgccjit log file. > 3 dump libgccjit reproducers." > > The first line is somewhat deceptive, as it doesn't say portions of > the backtrace will be anonymous; the backtrace is useful even if not > "debugging the compiler itself". And the description of level 1 says > it will also "dump pseudo C code", which I don't think is needed for > most of the debugging. Maybe we need an intermediate level that just > leaves the symbols without dumping the pseudo code? I think that's an excellent idea. > > > 0x09d82268: mov %edi,0x4(%esp) > > > 0x09d8226c: mov %eax,-0xe8(%ebp) > > > 0x09d82272: mov %edx,-0xe4(%ebp) > > > 0x09d82278: movl $0x2,(%esp) > > > 0x09d8227f: call *0x1318(%ebx) > > > 0x09d82285: mov %edx,-0xec(%ebp) <<<<<<<<<<<<<<<<<<<< > > > > So EDI is bunk at this point. Can you go back a bit further to where > > it's initialized? > > Sorry, I don't understand: I gave you the disassembly of 512 bytes > before, isn't that enough to see where EDI is assigned the value? Or > what do you mean by "go back"? It's not enough, no. we're looking for an insn of the form mov XXX, %edi or lea XXX, %edi, or anything like that. I'm suspicious because EDI is a register variable that is clobbered somehow right after a setjmp returned. Which setjmp implementation are you using? Is it possible that you're on Windows, but unlike other Windows setjmps, it's unsafe to call your setjmp through a function pointer? Pip