Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Joshua D. Boyd" <jdboyd@sigmaelectronics.com>
To: gdb@sourceware.org
Subject: Weird debugging problem
Date: Thu, 19 Oct 2006 19:48:00 -0000	[thread overview]
Message-ID: <1161287368.2428.43.camel@localhost.localdomain> (raw)

I am working on GNU/Linux 2.6.15 with GNU gdb 6.4-debian and gcc version
4.0.3.  I am trying to debug a threaded program that stops mysteriously
without stating a  particular fault.  My intention is that threads are
created during the programs start-up faze, then the same dozen or so
threads remain there the entire run time.  Prior to every
pthread_create, I print something to identify what thread is being
created at that time.

When I run the program in gdb, eventually (usually after running for 12+
hours), I get the following:
[New Thread -1734661200 (LWP 67296)]
Can't attach LWP 67296: No such process
(gdb) 
Now, if I'm not mistaken, that is not a valid process ID for Linux or
most other Unix type operating systems.

If I do a back trace at that point, it reports the current thread is the
main parent, which is currently in a nanosleep (and that thread's normal
behavior after start-up is to sleep most of the time and do house
keeping tasks when it wakes up).

At this point I am at a complete loss about what could be happening or
what to try next, so after scanning through archives and a short period
of lurking, I decided to hope that someone here could provide some
advice.


             reply	other threads:[~2006-10-19 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 19:48 Joshua D. Boyd [this message]
2006-10-19 19:56 ` Daniel Jacobowitz

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=1161287368.2428.43.camel@localhost.localdomain \
    --to=jdboyd@sigmaelectronics.com \
    --cc=gdb@sourceware.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