linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Luchjenbroers <adam@luchjenbroers.com>
To: linux-c-programming@vger.kernel.org
Subject: C/C++ Debugging techniques
Date: Wed, 12 Jun 2002 21:31:47 +0930	[thread overview]
Message-ID: <20020612115900Z317464-22020+2833@vger.kernel.org> (raw)
In-Reply-To: <20020604071008Z316528-22651+74173@vger.kernel.org>

I plan to start doing some debugging and stabilisation work on an open-source 
project. It provides the functionality I'm looking for but is incredibly 
unstable.

So I plan to attempt to fix the code. Before I started I thought I'd ask for 
advice on techniques for debugging code and how to make use of things such as 
core-dumps to find the problem. I hope to learn something from the advice 
people may give me.

       reply	other threads:[~2002-06-12 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020604071008Z316528-22651+74173@vger.kernel.org>
2002-06-12 12:01 ` Adam Luchjenbroers [this message]
2002-06-12 13:28   ` C/C++ Debugging techniques Elias Athanasopoulos
2002-06-13  4:04   ` chuckw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020612115900Z317464-22020+2833@vger.kernel.org \
    --to=adam@luchjenbroers.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).