Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!newsserver.jvnc.net!news.caren.net!news.join.ad.jp!wnoc-tyo-news!news.iij.ad.jp!fu.bekkoame.or.jp!pickwick.bekkoame.or.jp!si From: si@pickwick.bekkoame.or.jp (Shigeru IKEDA) Newsgroups: comp.unix.bsd.386bsd.misc Subject: Re: gdb debugger question (FreeBSD 2.0) Date: 16 Jul 1995 01:39:16 GMT Organization: Pickwick Club, Inc. Lines: 22 Message-ID: <SI.95Jul16103917@pickwick.bekkoame.or.jp> References: <rjb-0807952242030001@palpk-s13.intac.com> NNTP-Posting-Host: localhost.bekkoame.or.jp In-reply-to: rjb@intac.com's message of Sat, 08 Jul 1995 22:42:03 -0500 In article <rjb-0807952242030001@palpk-s13.intac.com> rjb@intac.com (Bob Badaracco) writes: >1. What compiler options do I need to turn on in order to generate a >symbol table for the debugger to use? -g (see gcc(1)) >2. When my program dies, how can I get the debugger to stop where it happens? gdb will automatically stop and bring you where your program dies. If your program generate core file, you must invoke gdb with "gdb YourProgram core", and bring you where core dump generated. >Any useful documentation available anywhere for this? I think gdb's manual in TeX format is in gdb's source distribution. -- Shigeru IKEDA <si@pickwick.bekkoame.or.jp> http://www.bekkoame.or.jp/~si PGP public key available upon request.