Does gdb 4.16 work with Solaris 2.4 unix threads?

Does gdb 4.16 work with Solaris 2.4 unix threads?

Post by Roger Moa » Thu, 07 Nov 1996 04:00:00

I'm using gdb version 4.16 to try to debug a multithreaded
application. I'm using unix threads with Solaris 2.4, and the
de* doesn't seem to recognize my other thread, i.e.

(gdb) info threads
* 1 process 1676  fini () at system.c:655

    Yet, there are two threads at this point. Both threads do execute,
it's just that gdb doesn't seem to know about the second one. Isn't it
suppose to keep track of these kinds of things? Any experience with
this? Do you think that POSIX threads (pthreads) would work (under

Thank you for any help,
Roger Moar.



1. gdb 4.16 error on Solaris 2.6

When I attempt to run gdb on my box I get the following error message
        Starting program: /usr/bin/d3
        /proc/00381: Resource temporarily unavailable.
        PIOCSTATUS or PIOCWSTOP failed.

Does anybody have any idea what might be causing this?

Sent via
Share what you know. Learn what you don't.

2. help! dependency problem when installing package kmailcvt.

3. Using gdb 4.16 with SparcWorks C++ 4.1?

4. How do I get X to work without monitor information?

5. gdb 4.16 CFLAGS

6. Apache, mySQL and PHP

7. GDB 4.16 vs glibc2.0.3 (segment fault??)

8. Q: K6 266 vs. K6-II 300

9. GDB 4.16 under glibc2.05 -> core dmp

10. gdb 4.16 and g++

11. help making gdb 4.16

12. problem compiling GDB 4.16 on "nearly 2.0"

13. Compiling gdb 4.16 with binutils