Re: [Xen-users] xen #13 (nov 18) segfaults on 'xm top' (x86_64)

[Jerone Young <jyoung5@xxxxxxxxxx>]

This is a race issue...between xentop & xenstore. Actually really easy
to recreate if you have a loop of creates & destroy the same
domain...working to fix now.

On Tue, 2005-11-22 at 17:28 +0100, Molle Bestefich wrote:
> Anybody has any clue what's going on here?
> 
> # xm top
> Segmentation fault
> 
> # strace xm top 2>&1 | tail -n 54
> access("/etc/terminfo/l/linux", R_OK)   = 0
> open("/etc/terminfo/l/linux", O_RDONLY) = 6
> read(6, "\32\1\24\0\35\0\20\0}\1)\3", 12) = 12
> read(6, "linux|linux console\0", 20)    = 20
> read(6, "\0\1\0\0\1\1\0\0\0\0\0\0\0\1\1\0\0\0\0\0\1\0\0\0\0\0\0"..., 29) = 29
> read(6, "\0", 1)                        = 1
> read(6, "\377\377\10\0\377\377\377\377\377\377\377\377\377\377\377"..., 32) = 
> 32
> read(6, "\377\377\0\0\2\0\4\0\25\0\32\0!\0%\0)\0\377\3774\0E\0G"..., 762) = 
> 762
> read(6, "\7\0\r\0\33[%i%p1%d;%p2%dr\0\33[3g\0\33[H\33[J"..., 809) = 809
> read(6, "", 1)                          = 0
> read(6, "", 10)                         = 0
> close(6)                                = 0
> ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fffffab5530) = -1 ENOTTY
> (Inappropriate ioctl for device)
> ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fffffab5500) = -1 ENOTTY
> (Inappropriate ioctl for device)
> ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fffffab6540) = -1 ENOTTY
> (Inappropriate ioctl for device)
> ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fffffab6540) = -1 ENOTTY
> (Inappropriate ioctl for device)
> ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fffffab6540) = -1 ENOTTY
> (Inappropriate ioctl for device)
> ioctl(2, SNDCTL_TMR_STOP or TCSETSW, {B0 -opost isig -icanon -echo
> ...}) = -1 ENOTTY (Inappropriate ioctl for device)
> rt_sigaction(SIGTSTP, NULL, {SIG_DFL}, 8) = 0
> rt_sigaction(SIGTSTP, {0x2aaaaacf4330, [], SA_RESTORER|SA_RESTART,
> 0x2aaaaae51ac0}, NULL, 8) = 0
> rt_sigaction(SIGINT, NULL, {SIG_DFL}, 8) = 0
> rt_sigaction(SIGINT, {0x2aaaaacf44d0, [], SA_RESTORER|SA_RESTART,
> 0x2aaaaae51ac0}, NULL, 8) = 0
> rt_sigaction(SIGTERM, NULL, {SIG_DFL}, 8) = 0
> rt_sigaction(SIGTERM, {0x2aaaaacf44d0, [], SA_RESTORER|SA_RESTART,
> 0x2aaaaae51ac0}, NULL, 8) = 0
> rt_sigaction(SIGWINCH, NULL, {SIG_DFL}, 8) = 0
> rt_sigaction(SIGWINCH, {0x2aaaaacf45d0, [], SA_RESTORER,
> 0x2aaaaae51ac0}, NULL, 8) = 0
> ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fffffab6620) = -1 ENOTTY
> (Inappropriate ioctl for device)
> ioctl(2, SNDCTL_TMR_STOP or TCSETSW, {B0 -opost isig -icanon -echo
> ...}) = -1 ENOTTY (Inappropriate ioctl for device)
> ioctl(2, SNDCTL_TMR_STOP or TCSETSW, {B0 -opost isig -icanon -echo
> ...}) = -1 ENOTTY (Inappropriate ioctl for device)
> gettimeofday({1132689370, 648479}, NULL) = 0
> mlock(0x7fffffab1c80, 48)               = 0
> mlock(0x7fffffab1cf0, 136)              = 0
> ioctl(3, SNDCTL_DSP_RESET, 0x7fffffab1c80) = 0
> munlock(0x7fffffab1c80, 48)             = 0
> munlock(0x7fffffab1cf0, 136)            = 0
> mlock(0x7fffffab1dd0, 18432)            = 0
> mlock(0x7fffffab1c70, 48)               = 0
> mlock(0x7fffffab1ce0, 136)              = 0
> ioctl(3, SNDCTL_DSP_RESET, 0x7fffffab1c70) = 0
> munlock(0x7fffffab1c70, 48)             = 0
> munlock(0x7fffffab1ce0, 136)            = 0
> rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
> write(4, "\6\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0", 16) = 16
> write(4, "\0", 1)                       = 1
> read(4, "\6\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0", 16) = 16
> read(4, "1\0", 2)                       = 2
> rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
> rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
> write(4, "\2\0\0\0\0\0\0\0\1\0\0\0\25\0\0\0", 16) = 16
> write(4, "/local/domain/0/name\0", 21)  = 21
> read(4, "\2\0\0\0\0\0\0\0\1\0\0\0\10\0\0\0", 16) = 16
> read(4, "Domain-0", 8)                  = 8
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users