From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30549 invoked by alias); 28 Feb 2014 16:33:43 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 30539 invoked by uid 89); 28 Feb 2014 16:33:43 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 28 Feb 2014 16:33:42 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EED86116543; Fri, 28 Feb 2014 11:33:40 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1HyIALNz0NxD; Fri, 28 Feb 2014 11:33:40 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 99FDD116423; Fri, 28 Feb 2014 11:33:40 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id C874EE03BD; Fri, 28 Feb 2014 08:33:39 -0800 (PST) Date: Fri, 28 Feb 2014 16:33:00 -0000 From: Joel Brobecker To: Johan Tibell Cc: gdb , Peter Wortmann Subject: Re: Making GDB recognize the Haskell DWARF source language ID Message-ID: <20140228163339.GC4860@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-02/txt/msg00068.txt.bz2 > We recently added DWARF output support to GHC, the main Haskell > compiler. However, GDB doesn't seem to respect the function names we > output as DWARF debug info and instead falls back to the symbol names. > My understanding is that this is due to the DWARF source language ID > we emit isn't recognized by GDB. Is this correct and, if so, how do we > remedy the situation? I am wondering if your issue might go deeper than just recognizing the language, but instead actually implement haskell support within GDB. Hard to tell without more details of what's going on. Perhaps a copy/past of a debugger sessions, annotated with what you would have expected would help give you more details. -- Joel