X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <47C421F4.7E50D1EB@dessent.net> Date: Tue, 26 Feb 2008 06:28:04 -0800 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gdb, no line numbers after gcc -g ??? References: <47C41CB6 DOT 1B6B8E05 AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hugh Sasse wrote: > OK, it works for a hello world, it says the symbols are loaded. > Therefore, as was most likely, I've munged something. How do I > interrogate object files to see which is/are missing the symbol data > (if that's what would throw everything else off the scent)? You can use "objdump -h file.o" and look at the sections. If you see .stab and .stabstr then you have STABS debug symbols (default for -g); if you have .debug_{abbrev,info,line,frame,pubnames,aranges,str} then you have Dwarf-2 debug symbols, which you get with -gdwarf-2 and are generally more sophisticated and better supported by gdb. If you see neither of those sets of sections, you have no debug data. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/