From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Tom E. Turner" Newsgroups: gmane.emacs.bugs Subject: DDD or IDE? (was Re: Build Failure) Date: Mon, 01 Jul 2002 13:39:16 -0400 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: <1020431829.514859@sj-nntpcache-5> <3CD2B8A1.E3BAC47@is.elta.co.il> <1020772560.927220@sj-nntpcache-5> <8296-Tue07May2002175828+0300-eliz@is.elta.co.il> <1020784405.676466@sj-nntpcache-3> <1024063905.30056@sj-nntpcache-5> <1024071857.503257@sj-nntpcache-3> <200206152147.g5FLlXE10974@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1025545296 22795 127.0.0.1 (1 Jul 2002 17:41:36 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 1 Jul 2002 17:41:36 +0000 (UTC) Cc: nicbrown@cisco.com, gnu-emacs-bug@prep.ai.mit.edu, faith@mit.edu, jm@mit.edu, tom@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17P5B9-0005vX-00 for ; Mon, 01 Jul 2002 19:41:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17P5Bb-0004zR-00; Mon, 01 Jul 2002 13:42:03 -0400 Original-Received: from tom by fencepost.gnu.org with local (Exim 3.34 #1 (Debian)) id 17P58u-0004df-00; Mon, 01 Jul 2002 13:39:16 -0400 Original-To: rms@gnu.org In-Reply-To: <200206152147.g5FLlXE10974@aztec.santafe.edu> (message from Richard Stallman on Sat, 15 Jun 2002 15:47:33 -0600 (MDT)) Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:2371 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:2371 I was wondering if anyone has successfully resolved build failures with the Data Display Debugger (DDD) or any IDE? http://linux.cis.nctu.edu.tw/docs/ddd/#Summary >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The Data Display Debugger (DDD) is a popular graphical user interface for command-line debuggers such as GDB, DBX, JDB, WDB, XDB, the Perl debugger, and the Python debugger. Besides ``usual'' front-end features such as viewing source texts, DDD has become famous through its interactive graphical data display, where data structures are displayed as graphs. A simple mouse click dereferences pointers or views structure contents, updated each time the program stops. Using DDD, you can reason about your application by watching its data, not just by viewing it execute lines of source code. Other DDD features include: debugging of programs written in Ada, C, C++, Chill, Fortran, Java, Modula, Pascal, Perl, and Python; machine-level debugging; hypertext source navigation and lookup; breakpoint, watchpoint, backtrace, and history editors; array plots; undo/redo; preferences and settings editors; program execution in terminal emulator window; debugging on remote host; on-line manual; extensive help on the Motif user interface; command-line interface with full editing, history, and completion capabilities. DDD is generally regarded as one of the best debuggers available. It is being used for software development by all major suppliers of information technology and is actively maintained by its co-author, Andreas Zeller at the Software Technology Dept., Technische Universitdt Braunschweig, Germany. Finally, DDD is free! DDD is open source software under the GNU license. All we'd like you to do do is to write a picture postcard. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Envelope-to: tom@gnu.org X-Authentication-Warning: aztec.santafe.edu: rms set sender to rms@aztec using -f From: Richard Stallman CC: gnu-emacs-bug@prep.ai.mit.edu Reply-to: rms@gnu.org Sender: bug-gnu-emacs-admin@gnu.org Date: Sat, 15 Jun 2002 15:47:33 -0600 (MDT) But the big question is, why when I use the default -O2 and don't specify --without-x does it built just fine !? the optimisation error obviously only relates to stuff that's included for emacs when there is no X support. any ideas? You can try compiling various files with different flags and determine which file is the locus of the problem. Then you can try splitting that file into two parts, compiling each part differently, and moving some things between the parts. then you can find which function is the locus of the problem. Then someone could study the erroneous assembler code made for that function and try to find the GCC bug. But before trying any of this, how about if you install the latest GCC release and see if it still fails. There is no point in your spending time to debug a GCC bug that has been fixed already. _______________________________________________ Bug-gnu-emacs mailing list Bug-gnu-emacs@gnu.org http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs