[Bug gdb/16053] gdb appears to hang at "attaching to program"

["sergiodj at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16053

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #8 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
(In reply to Eric Rossman from comment #7)
> (In reply to Sergio Durigan Junior from comment #5)
> > Oh, and BTW, you are using a very old kernel (2.6.16 was released in 2006),
> > so it might be worth checking for bugs related to ptrace in this kernel... 
> > Just FTR.
> 
> I'm in the process of getting a new machine running with a more current
> kernel, but in the meantime I was trying to keep things working for the
> existing machine.
> 
> I did read some about ptrace on 2.6.16 for user-mode kernel tracing, but
> nothing quite like this.

Yeah, well, since you are using SUSE, it might be worth filing a bug against
their Linux kernel/GDB.  Maybe they can provide a fix.

> > And one last thing I forgot to ask: I assume that starting the program
> > inside GDB works OK.  Right?
> 
> No, it doesn't work then either.
> 
> > gdb .execs/sleepsome 
> GNU gdb (GDB) 7.6.1
> Copyright (C) 2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "powerpc64-unknown-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/user/.execs/sleepsome...done.
> (gdb) break main
> Breakpoint 1 at 0x10000510
> (gdb) r
> Starting program: /home/user/.execs/sleepsome 
> 
> and then nothing. Only a SIGKILL gets it out of whatever state it is in.
> 
> I have a suspicion that the kernel is to blame, but for the next week or so,
> I cannot update the machine.


Well, I'd say the same.  strace uses the same ptrace options for attaching to
the inferior, and since it failed too, then it's probably not GDB's fault.

I will close this bug as INVALID, but please reopen it if you have any other
detail, or if you still see the problem after upgrading to the new machine.

Thanks a lot for the followup :-).

-- 
You are receiving this mail because:
You are on the CC list for the bug.