This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/837: solaris gcc3.2 64-bit
- From: guyarie at yahoo dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 18 Nov 2002 16:58:52 -0000
- Subject: gdb/837: solaris gcc3.2 64-bit
- Reply-to: guyarie at yahoo dot com
>Number: 837
>Category: gdb
>Synopsis: solaris gcc3.2 64-bit
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Nov 18 09:08:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: guyarie@yahoo.com
>Release: gdb 5.2.1
>Organization:
>Environment:
OS - SunOs 5.8 generic_108528_11 sun4u sparc SUNW,Ultra-S-10
GCC - 3.2 for sparc-sun-solaris2.8 posix threads
GDB - was configured as ... sparc-sun-solaris2.8
>Description:
Whenever compiling with -m64 flag, gdb fails to attach to the running process, displaying the following two lines after 'run':
procfs:4231 -- process not stopped.
procfs: ...giving up...
>How-To-Repeat:
I tried this with a minimal "Hello World" program, and it repeated itself.
More details:
1. If after running I type 'quit', it says "program running, kill anyway?"
2. If I type 'cont', it says:
procfs: couldn't find pid ... in procinfo list. If i check with ps I see that the pid is of the correct proc and it exists (in /proc as well).
3. When I try to manually attach gdb to the running process. I get the following error:
procfs: couldn't find pid 19908 (kernel thread 1) in procinfo list.
All the unix utils I use on processes work fine (pmap, etc.)
GDB works fine only if I don't use -m64 in the compilation.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: