From: Fabrice Gautier <gautier@email.enst.fr>
To: gdb@sources.redhat.com
Subject: Strange "info threads" behaviour. (linux]
Date: Fri, 04 May 2001 14:35:00 -0000 [thread overview]
Message-ID: <20010504232608.5AD1.GAUTIER@email.enst.fr> (raw)
Hi,
I'm using latest gdb snapshot to debug a program using libpthread.
I compiled gdb on a debian unstable box, adn debuging my programs works
fine. Info thread return correct informations.
But my goal is to use this progrma on a embdedd linux platform.
This platform uses a STPC CPU. It has a minimal filesystem, all libs and
binaries are directly copied from the debian box. Everything is the same
version than on the debian box. Kernels are both 2.4.3, but their config
are somewhat differents.
So when i run gdb on the STPC, when i type info threads i didn't get any
info. I didn't get an error neither. I just type "info threads", enter
and i get back to the gdb prompt..
How could this be explained?
Does some missing part of the system on the STPC platform could produce
this?
Thanks
--
Fabrice Gautier <gautier@email.enstfr>
next reply other threads:[~2001-05-04 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 14:35 Fabrice Gautier [this message]
2001-05-06 9:39 ` Mark Kettenis
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=20010504232608.5AD1.GAUTIER@email.enst.fr \
--to=gautier@email.enst.fr \
--cc=gdb@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