From: Keith Seitz <keiths@redhat.com>
To: Evan Lavelle <anti.spam1@dsl.pipex.com>
Cc: Insight List <insight@sources.redhat.com>
Subject: Re: Debugging threaded code on Linux
Date: Thu, 26 Jun 2003 14:28:00 -0000 [thread overview]
Message-ID: <1056638273.1571.2.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <3EFAD1BD.8040100@dsl.pipex.com>
On Thu, 2003-06-26 at 03:58, Evan Lavelle wrote:
> I'm having various problems debugging threaded code on Linux 2.4.7-10/RH
> 7.2, with insight 5.3. ddd seems to be more stable, but I think it's
> using an earlier version of gdb (5.0). The problems include fairly
> frequent crashes, 'thread apply' not working well, and so on.
>
> Does anyone have any experience of insight and LinuxThreads, and how
> stable it is? Should I be expecting this?
Make certain that the problems are in Insight. As far as I know, it is
very unlikely for the GUI part (Insight) to crash. More often than not,
it is the backend (gdb). Try debugging your program using command-line
gdb 5.3. (I think you can use "insight -nw" or "gdb -nw".)
Threads should work. Can you post a backtrace of the crash?
Keith
prev parent reply other threads:[~2003-06-26 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 10:58 Evan Lavelle
2003-06-26 14:28 ` Keith Seitz [this message]
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=1056638273.1571.2.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=anti.spam1@dsl.pipex.com \
--cc=insight@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).