From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Berndl, Klaus" Newsgroups: gmane.emacs.devel Subject: RE: repost: segfault on linux Date: Wed, 10 Mar 2004 10:23:56 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" X-Trace: sea.gmane.org 1079046419 20119 80.91.224.253 (11 Mar 2004 23:06:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 11 Mar 2004 23:06:59 +0000 (UTC) Cc: 'Emacs-Devel ' Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Mar 12 00:06:43 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1B1ZGF-0000Mo-00 for ; Fri, 12 Mar 2004 00:06:43 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1B1ZGF-0001A6-00 for ; Fri, 12 Mar 2004 00:06:43 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B1YJp-0005rJ-6v for emacs-devel@quimby.gnus.org; Thu, 11 Mar 2004 17:06:21 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B105J-0000tg-Py for emacs-devel@gnu.org; Wed, 10 Mar 2004 04:33:05 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B103N-0000Ye-Uf for emacs-devel@gnu.org; Wed, 10 Mar 2004 04:31:37 -0500 Original-Received: from [192.76.162.229] (helo=world1.sdm.de) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B0zwb-0007Zq-I5 for emacs-devel@gnu.org; Wed, 10 Mar 2004 04:24:05 -0500 Original-Received: from localhost ([127.0.0.1] helo=world1.sdm.de) (helo=world1.sdm.de) by world1.sdm.de (MTA) via esmtp id 1B0zwV-0002pH-5h; Wed, 10 Mar 2004 10:23:59 +0100 Original-Received: from mucns1.muc.sdm.de ([193.102.180.22]) (helo=mucns1.muc.sdm.de) by world1.sdm.de (MTA) via esmtp id 1B0zwT-0002p9-Kp; Wed, 10 Mar 2004 10:23:57 +0100 Original-Received: by mucns1.muc.sdm.de (MTA) via esmtp from localhost ([127.0.0.1] helo=sdmexch1.muc.sdm.de) id 1B0zwT-0000y2-J3; Wed, 10 Mar 2004 10:23:57 +0100 Original-Received: by sdmexch1.muc.sdm.de with Internet Mail Service (5.5.2653.19) id ; Wed, 10 Mar 2004 10:23:57 +0100 Original-To: 'Jens Lautenbacher ' , "'Kim F. Storm '" X-Mailer: Internet Mail Service (5.5.2653.19) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:20318 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:20318 Hmm, very mysterious... Jeff, Could you please test, if this bug occurs onyl with certain ECB-versions, so for exampe only with the new 2.22 and not with ECB 2.21 or vice versa or if the bug occurs regardless which ECB-version is installed? Does it only fail with current CVS Emacs or with the current release of Emacs 21 too. Have you tested it with XEmacs too? Have you tested it with a vanilla Emacs, means started by emacs -q -no-site-file and then just loading ECB and nxml-mode and nothing more? Jeff, could you please answer to these questions? Thanks a lot! Could you please file me a complete problem-report via `ecb-sumbit-problem-report' so i can see your configuration of ECB and some of the Emacs-internal-states? Ciao, Klaus -----Original Message----- From: Jens Lautenbacher To: Kim F. Storm Cc: Emacs-Devel; Berndl, Klaus Sent: 10.03.2004 10:10 Subject: Re: repost: segfault on linux On Mon, 2004-03-08 at 18:34, Kim F. Storm wrote: > Jens Lautenbacher writes: > > When trying to use James Clarks nxml mode (nxml-mode-20031031) with > > syntax highlighting turned on, current CVS emacs segfaults with the > > following stacktrace. please tell me if I should provide more > > information (this is CVS from today, on Fedora Core I, emacs built with > > gtk enabled) > > As always, it would be helpful if you tried to give a more precise > recipe for reproducing this -- and also tried to narrow down exactly > what data causes this crash to occur. > > Also have a a look at etc/DEBUG for advise on trying to debug > this a little further yourself. OK, I will not be of much help when it comes down to the C side of things, but I try to explain better what leads to the segfault. First of all, it only happens when the syntax highlighting is on in nxml. Second, it only happens when ECB is also running, and the xml file is loaded by clicking on a xml file name in ECB's history or directory buffer. It does NOT happen when ECB runs and I simply find-file a xml file. So it may be the question if it's nxml or ECB's fault here, but on the other hand I suppose a segfault is not an acceptable response :-) I tried to look at the debugger output some more (with CVS emacs as of today, compiled without optimization and only "-g"), and the stacktrace looks a bit different from what I saw the last time Program received signal SIGSEGV, Segmentation fault. 0x08203e7c in find_interval (tree=0x9fc13cc, position=1) at intervals.c:652 652 tree = balance_possible_root_interval (tree); (gdb) l 647 648 if (relative_position > TOTAL_LENGTH (tree)) 649 abort (); /* Paranoia */ 650 651 if (!handling_signal) 652 tree = balance_possible_root_interval (tree); 653 654 while (1) 655 { 656 if (relative_position < LEFT_TOTAL_LENGTH (tree)) (gdb) where #0 0x08203e7c in find_interval (tree=0x9fc13cc, position=1) at intervals.c:652 #1 0x08207ead in validate_interval_range (object=-1982984752, begin=0xbf6000b0, end=0xbf6000b0, force=0) at textprop.c:181 #2 0x08208ab4 in Ftext_properties_at (position=1, object=-1982984752) at textprop.c:585 #3 0x08208b83 in Fget_text_property (position=1, prop=675635440, object=-1982984752) at textprop.c:606 #4 0x081054f3 in face_at_buffer_position (w=0x9dbb6d8, pos=1, region_beg=-1, region_end=-1, endptr=0xbf600200, limit=101, mouse=0) at xfaces.c:7313 #5 0x0809a5fc in handle_face_prop (it=0xbfecc670) at xdisp.c:2841 #6 0x08099f67 in handle_stop (it=0xbfecc670) at xdisp.c:2567 #7 0x0809f96e in next_element_from_buffer (it=0xbfecc670) at xdisp.c:5439 #8 0x0809e641 in get_next_display_element (it=0xbfecc670) at xdisp.c:4791 (gdb) p *tree $2 = {total_length = 32, position = 14, left = 0x9fc13b0, right = 0x9fc13e8, up = {interval = 0x89ce0dd0, obj = -1982984752}, up_obj = 1, gcmarkbit = 0, write_protect = 0, visible = 0, front_sticky = 0, rear_sticky = 0, plist = 675635056} Thank god I'm a java guy, so I don't know much about C and C debugging anymore, but doesn't the tree->up->obj look strange?