From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Kalman Reti" Newsgroups: gmane.emacs.devel,gmane.emacs.bugs Subject: Re: mark_object crash in 22.1 and latest CVS (as of tonight) Date: Fri, 16 Nov 2007 09:07:08 -0500 Message-ID: <16af2f430711160607m158b9c98xa401166709f628ff@mail.gmail.com> References: <16af2f430711081955j3d5e6745gc0f7a50e02d9a892@mail.gmail.com> <16af2f430711120340q27926877tf976ef397d12df16@mail.gmail.com> <16af2f430711140939x45663644je0dce25c8796b18@mail.gmail.com> <16af2f430711141700g74175advd8f234478293faa5@mail.gmail.com> <16af2f430711160405p6a734839lb24610ee65257498@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1195222051 11770 80.91.229.12 (16 Nov 2007 14:07:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 16 Nov 2007 14:07:31 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org, kalman.reti@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 16 15:07:35 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1It1qz-0000YY-CQ for ged-emacs-devel@m.gmane.org; Fri, 16 Nov 2007 15:07:29 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1It1qm-0007bE-Ek for ged-emacs-devel@m.gmane.org; Fri, 16 Nov 2007 09:07:16 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1It1qi-0007b8-Q7 for emacs-devel@gnu.org; Fri, 16 Nov 2007 09:07:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1It1qg-0007ao-Bt for emacs-devel@gnu.org; Fri, 16 Nov 2007 09:07:11 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1It1qg-0007ai-5I for emacs-devel@gnu.org; Fri, 16 Nov 2007 09:07:10 -0500 Original-Received: from nz-out-0506.google.com ([64.233.162.237]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1It1qf-0000LE-P1 for emacs-devel@gnu.org; Fri, 16 Nov 2007 09:07:10 -0500 Original-Received: by nz-out-0506.google.com with SMTP id f1so836604nzc for ; Fri, 16 Nov 2007 06:07:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=AM4sJzhzsd/ETtEOWkZnbAGobE8FUtfZqbY838NKimA=; b=b/Xz46suEnoH20M8ngPmQp3zuA8B8L9UF5rhdjOq7WC6bEhDIeZjq+L0dVworaz3R6NILkFxsvgmFD3bCC7ccL1saCtKNYmaWmhOpaouLWp1N0OoKT06sHNLRTLxnjpA/4Wnj1S6MPXsOZwkAzmS6btx6gabIYzwGSnwh1AW7YY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=K3TKLKI5tZAOdqVjxh5GDFjsmmQzl6OEKPee7wqJWn+peXmjp2c8XJd0EkZRnBNzFKwoJ02ptS6L/4iNDk8SNZhZPAGVcP9cEgp6h5DLNJggSTKhy88IrWvwqC7MloFu5bWJy29N34B/70QtgAUaAhpI+eZvm8qFBMKM1+JiRBc= Original-Received: by 10.143.161.3 with SMTP id n3mr555521wfo.1195222028320; Fri, 16 Nov 2007 06:07:08 -0800 (PST) Original-Received: by 10.143.167.19 with HTTP; Fri, 16 Nov 2007 06:07:08 -0800 (PST) In-Reply-To: <16af2f430711160405p6a734839lb24610ee65257498@mail.gmail.com> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:83343 gmane.emacs.bugs:16991 Archived-At: On Nov 16, 2007 7:05 AM, Kalman Reti wrote: > One thing that isn't > clear to me is exactly who is calling set-match-data with the reseat > argument set to evaporate inside of the shell-command function. This is > happening somewhere inside of the shell-command function which my > code calls. > I just figured this part out. The save-match-data macro generates an unwind-protect call to set-match-data with 'evaporate as a second argument. What I haven't figured out is why these are mostly OK. Perhaps it is just a garbage collection being kicked of at an inconvenient time?