X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 26 Feb 2008 14:43:14 +0000 (WET) From: Hugh Sasse To: cygwin@cygwin.com Subject: Re: gdb, no line numbers after gcc -g ??? In-Reply-To: <47C421F4.7E50D1EB@dessent.net> Message-ID: References: <47C41CB6.1B6B8E05@dessent.net> <47C421F4.7E50D1EB@dessent.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, 26 Feb 2008, Brian Dessent wrote: > 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. I see what's happened now. I tried to add a --enable-extra-pe-debug which didn't work, complaining about a -f option, so I put the whole thing in quotes. I've thrown that option out now, and my image.o now has stabs information, so I can proceed now. Thank you. > > Brian > Hugh -- 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/