Bug 81429 – gdb complains about undefined symbol: ps_get_thread_area

Bug 81429 - gdb complains about undefined symbol: ps_get_thread_area

Summary:	gdb complains about undefined symbol: ps_get_thread_area

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	gdb (Show other bugs)
Sub Component:
Version:	phoebe
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Elena Zannoni
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	79579
	Show dependency tree / graph

Reported:	2003-01-09 07:54 EST by Need Real Name
Modified:	2015-01-07 19:02 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-01-20 10:28:59 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2003-01-09 07:54:02 EST

Description of problem:
gdb complains about been unable to debug pthreads.

Version-Release number of selected component (if applicable):
gdb-5.3post-0.20021129.4

How reproducible:
$ cat > test.c
#include <stdio.h>
int main(void)
{
  printf("test\n");
  return 0;
}
$ gcc -g test.c
$ gdb a.out

Comment 1 Elena Zannoni 2003-01-10 12:09:30 EST

Yes, this is (unfortunately) expected behavior. Gdb has not been ported yet to
work with the new NPTL thread library.
However, gdb should behave correctly if the program has no threads.

Comment 2 Shawn Walker 2003-01-20 02:39:59 EST

What's the timeframe looking like on getting GDB to work with the new threaded
system?

Comment 3 Elena Zannoni 2003-01-20 10:28:59 EST

There is a patch in the next beta.
I am closing this bug report. If there are more problems, let's open new ones,
against the next beta.

Note You need to log in before you can comment on or make changes to this bug.