From: teg@redhat.com (Trond Eivind Glomsrød)
To: "Oldham, Adam" <adam.oldham@marconi.com>
Cc: "'gdb@sourceware.cygnus.com'" <gdb@sourceware.cygnus.com>
Subject: Re: gdb 5, linuxthreads, working??
Date: Fri, 25 May 2001 14:25:00 -0000 [thread overview]
Message-ID: <xuyhey9w27g.fsf@halden.devel.redhat.com> (raw)
In-Reply-To: <A3E34B558F5CD211B4980008C7A4A99003883A1A@sparrow.eng.gilbarco.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
"Oldham, Adam" <adam.oldham@marconi.com> writes:
> Hello,
> I've tried to read as far back as I could in the gdb lists and in newsgroups
> and I cannot figure out what is wrong, so any help would be appreciated. I
> am currectly running Mandrake 7.2 with kernel 2.2.17, glibc 2.1.3, gcc
> 2.95.2, gpc 20010502, and gdb 5. I have a heavy program I have written to
> utilize linuxthreads and calls pthread_create to run the threads. When
> debugging the program with gdb 5 (both the binary distributed with Mandrake
> and compiling from source) i get this with my executable:
> ...
> This GDB was configured as "i686-pc-linux-gnu"...rw_common (): write: No
> such file or directory.
>
> warning: unable to set global thread event mask
> [New Thread 1024 (runnable)]
> rw_common (): write: No such file or directory.
>
> warning: stop_or_attach_thread: generic error
> (gdb)
Sounds like something in Mandrake is broken - thread debugging works
in Red Hat Linux 7.1 (although it certainly could be better - and you
the gdb from Rawhide to get support for more than 32 threads).
--
Trond Eivind Glomsrød
Red Hat, Inc.
next prev parent reply other threads:[~2001-05-25 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 13:38 Oldham, Adam
2001-05-25 14:25 ` Trond Eivind Glomsrød [this message]
2001-05-25 14:37 ` Kevin Buettner
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=xuyhey9w27g.fsf@halden.devel.redhat.com \
--to=teg@redhat.com \
--cc=adam.oldham@marconi.com \
--cc=gdb@sourceware.cygnus.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