From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.bugs Subject: bug#41321: 27.0.91; Emacs aborts due to invalid pseudovector objects Date: Sun, 24 May 2020 19:40:09 +0000 Message-ID: References: <83zha8cgpi.fsf@gnu.org> <83r1vibmyj.fsf@gnu.org> <83imgublku.fsf@gnu.org> <831rncjuwf.fsf@gnu.org> <83h7w5xvfa.fsf@gnu.org> <83y2phwb9x.fsf@gnu.org> <83r1v9w9vi.fsf@gnu.org> <83mu5xw50d.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="120445"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 41321@debbugs.gnu.org, Stefan Monnier To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun May 24 21:41:47 2020 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 1jcwVF-000VD8-Bv for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 24 May 2020 21:41:45 +0200 Original-Received: from localhost ([::1]:34034 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jcwVE-0005QB-E0 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 24 May 2020 15:41:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38644) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jcwUY-0004jI-BB for bug-gnu-emacs@gnu.org; Sun, 24 May 2020 15:41:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55523) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jcwUY-0001xA-0D for bug-gnu-emacs@gnu.org; Sun, 24 May 2020 15:41:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jcwUX-0000iz-TC for bug-gnu-emacs@gnu.org; Sun, 24 May 2020 15:41:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 24 May 2020 19:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 41321 X-GNU-PR-Package: emacs Original-Received: via spool by 41321-submit@debbugs.gnu.org id=B41321.15903492592771 (code B ref 41321); Sun, 24 May 2020 19:41:01 +0000 Original-Received: (at 41321) by debbugs.gnu.org; 24 May 2020 19:40:59 +0000 Original-Received: from localhost ([127.0.0.1]:38836 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jcwUV-0000ib-AD for submit@debbugs.gnu.org; Sun, 24 May 2020 15:40:59 -0400 Original-Received: from mail-ot1-f42.google.com ([209.85.210.42]:35318) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jcwUN-0000i6-He for 41321@debbugs.gnu.org; Sun, 24 May 2020 15:40:51 -0400 Original-Received: by mail-ot1-f42.google.com with SMTP id 69so12413225otv.2 for <41321@debbugs.gnu.org>; Sun, 24 May 2020 12:40:51 -0700 (PDT) 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=SaNZTZAk2E3O2TYeOuZFzDNnTA50frPGKHaWomX1xvA=; b=X43FyVEzcEOQaRzGIvKrCRT2ryAyUoHajfvhFXI7ebUA7EY7ogcVjuMZgC38tQrq6j japlsINL69qcpPl97+Qg3sEBt8IAylBrYVTuJpS5efIHC/cvRHraHfsoNO2/++8soBsG 8aVBGz05Fsxo7gP8aLkVDtGH53hKnpo56yp+quOJLsh5DHQNoZ3Invq/VDeW4KuGmbBU Rf2K5NLPBhFVkR6xesFTJ8mxxNpU1Ra4ggPyepCU+Fa3UvrIKlS09l8KZtKcOOaMAc1g BsX55qcaFYwgSghyU4+UQbUqlf+DeLZS2axgU861UlAplnIyNtKZ/Svc20Pa7ezgwfkW Q78g== 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=SaNZTZAk2E3O2TYeOuZFzDNnTA50frPGKHaWomX1xvA=; b=KIjzf/UeBGdZ+H/smk2iw41OIcEusEEyID5C1e66xVw+7guiFUxHgRsLwC0pYJ5UjD X7TUE5waiYBaBMiEMr25E6JqwNiCCEd3WCZ2Wy/9gC/DUiRc0JhS7vhlxBuvNSlHo2/P frVtCNjJlNvnOguCkOvRZ8RxdfNZVQQKjFsYR3Dw12R9Ao7TZ89BQnBg88XfHmvNblds b9f5dCCYGucu4UrFKlXvImsjWdtALscM2I4DBi83ZUxe2+yHm/jJYgEYI28FXBhZsMfb hINk/LZ0y9Ffr2H0StupKeRuDxFbUAwnVpHSkjw3rY4hz6FVdPEcWVNf7wpEu2rfu5XR kXqw== X-Gm-Message-State: AOAM531MModdUA0/qdT0xiL1wuY1xd9O1lOAJVoODrmhzPEatstQG/uG IFpTSqo971l8RNBadO9VoNG0+BH8JhCODwV6z9U= X-Google-Smtp-Source: ABdhPJy8KiErZokPJLEvxcIoUTikGtPpmMsloPI6tUEpOuo1HZegWBV/aIYwdaPgmF9JkKH7Hn4watafC7+7K42VrWM= X-Received: by 2002:a05:6830:61b:: with SMTP id w27mr16605196oti.154.1590349245522; Sun, 24 May 2020 12:40:45 -0700 (PDT) In-Reply-To: <83mu5xw50d.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:180924 Archived-At: On Sun, May 24, 2020 at 6:40 PM Eli Zaretskii wrote: > > From: Pip Cet > > Date: Sun, 24 May 2020 18:03:57 +0000 > > Cc: 41321@debbugs.gnu.org, Stefan Monnier > > > > > If you still claim that I didn't demonstrate that the buffer's overlay > > > chain got corrupted > > > > I do, of course. The message GDB prints simply does not say anything > > problematic about the buffer's overlay chain. > > > > > as part of the bug that caused the segfault, > > > please point out what I missed here. > > > > You omitted the third call to xtype, which was even more clearly > > nonsensical: xtype was misbehaving. We don't know in which way it was > > misbehaving. So there's no evidence either way. > > > > FWIW, running into gdb bugs is something that happens to me almost on > > a regular basis. There's no point reporting those, as there's > > generally no response. In your case, you're in an unusual environment > > with a rather large and complicated .gdbinit file which does very > > strange things to avoid running into GDB bugs that we know about. All > > that increases the likelihood of your encountering a gdb bug that no > > one else has, or that has been reported but never responded to. > > I don't buy this, sorry. So you think there's a second bug, located in Emacs, which causes GDB, which isn't supposed to be broken by anything the debuggee does, to be broken and respond in nonsensical ways? > I use GDB every day in this very "unusual > environment", both when debugging Emacs and other programs. And you've never run into GDB bugs? > The > probability of these being due to some bug in GDB or in .gdbinit > commands is very low, as I and others use them all the time. I'm perfectly willing to help you trace down this bug (in GDB or .gdbinit; we've already found the bug in mingw and the one in Emacs) if it serves any purpose, but I suspect you don't have the time. But I can't conceive of an explanation in which a bug in Emacs could cause a bug-free GDB to respond in the nonsensical way your last invocation of xtype did. > It is much more probable that the commands I've shown are signs of a real > trouble in Emacs and not in GDB. Are you saying the bug I've found isn't "a real trouble"? I'm curious as to what trouble you're imagining. > I'm not willing to disregard what > those commands show me because they don't match your theory. What they show you is that memory at a certain address, which they helpfully specify, isn't mapped. You conclude that memory at a totally different address isn't mapped, even though GDB quite explicitly never says so. That conclusion is invalid.