edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] gdb
Date: Fri, 4 Sep 2015 22:46:34 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1509042244260.25982@carhart.net> (raw)



I noticed Tyler's gdb prompt and I was wondering, do any of you swear by 
gdb, is this how you usually develop and debug edbrowse?
Are there any alternatives that are pure command line or curses?

thanks
Kevin


--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists

             reply	other threads:[~2015-09-05  5:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-05  5:46 Kevin Carhart [this message]
2015-09-05  7:15 ` Karl Dahlke
2015-09-05 11:54   ` Adam Thompson

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=alpine.LRH.2.03.1509042244260.25982@carhart.net \
    --to=kevin@carhart.net \
    --cc=edbrowse-dev@lists.the-brannons.com \
    /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).