This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2139: get _PROCEDURE_LINKAGE_TABLE_ error when running on multi-processor Sparc
- From: michael_h_cline at raytheon dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 27 Jun 2006 16:58:40 -0000
- Subject: gdb/2139: get _PROCEDURE_LINKAGE_TABLE_ error when running on multi-processor Sparc
- Reply-to: michael_h_cline at raytheon dot com
>Number: 2139
>Category: gdb
>Synopsis: get _PROCEDURE_LINKAGE_TABLE_ error when running on multi-processor Sparc
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jun 27 17:08:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Michael Cline
>Release: gdb 6.2
>Organization:
>Environment:
Solaris 5.8
>Description:
I have multi-threaded code, where I set a breakpoint, "run" to the breakpoint, then hit next from 2-10 times on any code (say a for loope). I will inevitably get the error: "in _PROCEDURE_LINKAGE_TABLE_ () from usr/lib/libthread.so.1". Nothing really works after this point. Hitting "up" results in "<signal handler called>". Hitting "up" again, puts me back at my code where I would expect. But I cant continue.
This problem only shows on Solaris machines that have >1 processor in them!
I do not have any problems on Solaris machines that have only 1 processor.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: