doutuo8800 2014-09-25 15:01
浏览 42
已采纳

log.Flags()是否应该与write共享相同的sync.Mutex?

I have the following code:

package main

import(
    "log"
    "os"
)

type LogFilter struct {}

func (t *LogFilter) Write(p []byte) (int, error) {
    _ = log.Flags()
    return os.Stderr.Write(p)
}

func main() {
    log.SetOutput(&LogFilter{})
    log.Println("Hello, playground")
}

Which Deadlocks because of http://golang.org/src/pkg/log/log.go line 135 defers the lock until after the write. Which in the write I'm calling Flags which tried to get the lock.

Is there any reason that they (Write & Flags) should share the same mutex?

  • 写回答

1条回答 默认 最新

  • dongzhenjian5195 2014-09-25 15:20
    关注

    It shares the mutex, because the Logger also reads its internal flags field when writing output.

    Granted it could be more granularly locked, but you'd have to make a good case to justify the added complication. If you need the flags in your filter, I would copy them in when you initialize your structure.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 请教一下各位,为什么我这个没有实现模拟点击
  • ¥15 执行 virtuoso 命令后,界面没有,cadence 启动不起来
  • ¥50 comfyui下连接animatediff节点生成视频质量非常差的原因
  • ¥20 有关区间dp的问题求解
  • ¥15 多电路系统共用电源的串扰问题
  • ¥15 slam rangenet++配置
  • ¥15 有没有研究水声通信方面的帮我改俩matlab代码
  • ¥15 ubuntu子系统密码忘记
  • ¥15 保护模式-系统加载-段寄存器
  • ¥15 电脑桌面设定一个区域禁止鼠标操作