Bug #1578

Confusing gdb detach message

Added by hasso over 5 years ago. Updated about 1 month ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Userland
Target version:4.2.x

Description

(gdb) ^Dquit
The program is running. Quit anyway (and detach it)? (y or n) y
Detaching from program: /pfs/@@-1:00003/pkg/bin/myprog, process 1354

History

#1 Updated by corecode over 5 years ago

Hasso Tepper wrote:
> (gdb) ^Dquit
> The program is running. Quit anyway (and detach it)? (y or n) y
> Detaching from program: /pfs/@@-1:00003/pkg/bin/myprog, process 1354

Is your /usr a symlink or a null mount? Works properly here with a null
mount.

cheers
simon

#2 Updated by hasso over 5 years ago

null mount:
/pfs/@@-1:00003 on /usr (null, local)

Still reproduceable with the latest master. Execute the app
from /usr/pkg/bin/* (a lot of X apps normally), attach dgb to it (gdb -p) and
then quit from gdb.

#3 Updated by tuxillo about 1 month ago

  • Description updated (diff)
  • Category set to Userland
  • Status changed from New to Closed
  • Assignee deleted (0)
  • Target version set to 4.2.x

Hi,

Seems things are a bit better now:

(gdb) attach 197023
Attaching to process 197023
Reading symbols from /pfs/@@-1:00003/pkg/bin/myprog...done.
Reading symbols from /lib/libc.so.8...done.
Loaded symbols for /lib/libc.so.8
Reading symbols from /libexec/ld-elf.so.2...done.
Loaded symbols for /libexec/ld-elf.so.2
0x00000008008ba74c in nanosleep () at nanosleep.S:2
warning: Source file is more recent than executable.
2 RSYSCALL(nanosleep)
(gdb) quit
A debugging session is active.

Inferior 1 [process 197023] will be detached.

Quit anyway? (y or n) y
Detaching from program: /pfs/@@-1:00003/pkg/bin/myprog, process 197023
andromeda# df -hT .
Filesystem Type Size Used Avail Capacity Mounted on
/pfs/@@-1:00003 null 94G 46G 48G 49% /usr
[1] + Exit 255 ./myprog

Closing this one.

Cheers,
Antonio Huete

Also available in: Atom PDF