dtl19910708 2016-01-28 09:31
浏览 178

恐慌中的恐慌

When running an http server in Go (go1.2.1 linux/amd64) I get a rare error.

unexpected fault address 0xb84004
fatal error: fault
[signal 0x7 code=0x2 addr=0xb84004 pc=0x421d62]

goroutine 1 [running]:
unexpected fault address 0xacb59c
panic during panic

This only happened once, so far, after almost a week of running and is not reproducible. However, I would still like to know what this means and how this could happen. Unfortunately I cannot provide any code sample, since I don't know where it might occur and the code is not open source (yet), so I'm looking for a more general answer. Anyone?

  • 写回答

1条回答 默认 最新

  • douou9094747 2017-10-20 04:24
    关注

    Kernel version:

    Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux

    Meet several different when Running:

    traefik_linux-arm64 --configFile=/etc/traefik.toml

    Error 1:

    fatal error: fatal error: unexpected signal during runtime execution
panic during panic

goroutine 0 [idle]:
fatal error: unexpected signal during runtime execution
stack trace unavailable

    Error 2:

    qemu: unhandled CPU exception 0x10004 - aborting
PC=0000000000060688  SP=00000040008002d0
X00=000000000000001e X01=00000000027a5df0 X02=0000000000000001 X03=0000000000000000
X04=0000000000000001 X05=0000000000000004 X06=0000000000000001 X07=00000144200180b0
X08=00000000027a68c0 X09=00000144200180a8 X10=0000000000000000 X11=0000000000000000
X12=0000000000000000 X13=000001441fffc4fd X14=0000000000000008 X15=0000000000000000
X16=0000004000800328 X17=00000040008003a0 X18=0000000000000000 X19=0000000000000000
X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000
X24=0000000000000000 X25=0000000000000000 X26=000000000187aab0 X27=00000000027c735c
X28=00000000027a61a0 X29=0000000000000000 X30=000000000001d964 PSTATE=80000000 (flags N---)

Aborted

    Error 3:

    Segmentation fault

    Error 4:

    /build/qemu-XXUWBP/qemu-2.1+dfsg/tcg/optimize.c:434: tcg fatal error
Aborted

    Error 5:

    fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x581c4af8 pc=0x61544]

runtime stack:
github.com/containous/traefik/vendor/github.com/miekg/dns.packSaltWire(0x7, 0x35b98, 0x0, 0xaa1195a646299, 0x1660, 0x3b9bc, 0x144200004b8)
    /go/src/github.com/containous/traefik/vendor/github.com/miekg/dns/nsecx.go:117 +0x78

goroutine 1 [runnable, locked to thread]:
runtime.init.2()
    /usr/local/go/src/runtime/panic.go:180 +0x84
runtime.init()
    <autogenerated>:1 +0xe0
runtime.main()
    /usr/local/go/src/runtime/proc.go:141 +0xc0
runtime.goexit()
    /usr/local/go/src/runtime/asm_arm64.s:931 +0x4

    Error 6:

    fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
SIGILL: illegal instructionfatal: morestack on g0

fatal: morestack on g0
PC=0x14420008d80fatal: morestack on g0
 m=1fatal: morestack on g0
 sigcode=2fatal: morestack on g0


fatal: morestack on g0
goroutine 0fatal: morestack on g0
 [idlefatal: morestack on g0
]:

fatal: morestack on g0
goroutine 1fatal: morestack on g0
 [runnablefatal: morestack on g0
, locked to thread]:
fatal: morestack on g0
fatal: morestack on g0
fatal: morestack on g0
runtime.init.1fatal: morestack on g0
()
fatal: morestack on g0
    /usr/local/go/src/runtime/mstats.gofatal: morestack on g0
:438fatal: morestack on g0
 +0xc8fatal: morestack on g0

runtime.init()
fatal: morestack on g0
    fatal: morestack on g0
<autogenerated>:fatal: morestack on g0
1 +0xdc
fatal: morestack on g0
runtime.main(fatal: morestack on g0
)
    fatal: morestack on g0
/usr/local/go/src/runtime/proc.go:fatal: morestack on g0
141 +0xc0fatal: morestack on g0

fatal: morestack on g0
runtime.goexit(fatal: morestack on g0
)
    /usr/local/go/src/runtime/asm_arm64.sfatal: morestack on g0
:931 +fatal: morestack on g0
0x4
fatal: morestack on g0

r0      fatal: morestack on g0
0x0
fatal: morestack on g0
r1      0x0fatal: morestack on g0

r2      fatal: morestack on g0
0x14420000300
fatal: morestack on g0
r3      0x14420008d68fatal: morestack on g0

r4      fatal: morestack on g0
0x14420008d68
r5      fatal: morestack on g0
0x14420002000
fatal: morestack on g0
r6      0xf4240fatal: morestack on g0

r7      fatal: morestack on g0
0x0
fatal: morestack on g0
r8      0x48fatal: morestack on g0

r9      fatal: morestack on g0
0x0
r10     fatal: morestack on g0
0x14420050000
r11     fatal: morestack on g0
0x14420000480
fatal: morestack on g0
r12     0x3b970fatal: morestack on g0

r13     fatal: morestack on g0
0x1441fffffd0fatal: morestack on g0

r14     fatal: morestack on g0
0x8
fatal: morestack on g0
r15     0x0fatal: morestack on g0

r16     fatal: morestack on g0
0x14420008d00
r17     fatal: morestack on g0
0x0
fatal: morestack on g0
r18     0x0fatal: morestack on g0

r19     fatal: morestack on g0
0x0
fatal: morestack on g0
r20     0x0fatal: morestack on g0

r21     fatal: morestack on g0
0x0
r22     fatal: morestack on g0
0x0
r23     fatal: morestack on g0
0x0fatal: morestack on g0

r24     fatal: morestack on g0
0x0
r25     fatal: morestack on g0
0x0
fatal: morestack on g0
r26     0x187ab40fatal: morestack on g0

r27     0x27c72b6fatal: morestack on g0

r28     fatal: morestack on g0
0x14420000300
fatal: morestack on g0
r29     0x14420009fe0fatal: morestack on g0

lr      fatal: morestack on g0
0x14420008d80
fatal: morestack on g0
sp      0x14420008ca0fatal: morestack on g0

pc      fatal: morestack on g0
0x14420008d80
fatal: morestack on g0
fault   0x0fatal: morestack on g0

    Error etc. OMG

    评论

报告相同问题？

  • 了解Golang恐慌
    2018-04-26 10:01
    回答 1 已采纳 The panic stack: panic: runtime error: invalid memory address or nil pointer dereference [signal
  • 测试从恐慌中恢复
    2015-07-29 16:29
    回答 3 已采纳 I would say that designing API for library that relies on panic/recover is not a right way. Go has
  • 类型断言恐慌
    2017-05-24 18:55
    回答 1 已采纳 When you return a BaseInterface from a function, the type of the reference is actually BaseInterfa
  • 恐慌
    2021-02-20 07:12
    恐慌
  • 如何在Golang中测试恐慌？ json
    2017-07-12 08:39
    回答 2 已采纳 Use recover(). func Testgood_PanicStatement(t *testing.T) { Convey("And Invalid Json return err
  • 我如何处理goroutine中的恐慌？
    2019-02-06 17:20
    回答 1 已采纳 You are using recover correctly. You have two problems: You are using panic incorrectly. You sho
  • 恐慌并从包裹中恢复
    2014-09-26 20:51
    回答 2 已采纳 The application must call recover directly from the deferred function to handle the panic. The s
  • 波动率/恐慌指数VIX数据
    2020-06-14 11:18
    波动率/恐慌指数VIX数据 - 根据实盘原始股票期权行情数据计算VIX从2015-01至2020-06（持续更新中...) - 根据[White Paper Cboe Volatility Index](http://www.cboe.com/micro/vix/vixwhite.pdf) - 数据格式为bson...
  • golang gorp插入恐慌
    2015-07-09 16:16
    回答 1 已采纳 This error; reflect.Value.Interface: cannot return value obtained from unexported field or method
  • 在结构中打印nil错误时出现恐慌
    2019-01-25 16:08
    回答 2 已采纳 In tc, you're embedding a value of type error. Sprintf sees that tc implements error (because of e
  • 在Golang赶上恐慌
    2014-07-29 21:42
    回答 7 已采纳 Go is not python, you should properly check for args before you use it: func main() { if len(
  • python恐慌指数计算VIX.zip
    2021-07-18 10:27
    python 恐慌指数计算VIX
  • 在Web应用程序中使用恐慌
    2014-11-04 13:56
    回答 2 已采纳 Is there anything I miss so this approach won't work well? That is discussed today (!) Nov. 4
  • 恐慌模拟器：通过一个出口模拟可修改房间中的恐慌行为-matlab开发
    2021-06-01 09:54
    恐慌模拟器的目的是模拟人类在只有一个出口的拥挤环境中逃离恐慌的特征，例如浴室、迪斯科舞厅、体育场、演讲厅或一般房间。 因此，行人行为的建模受到 Helbing 等人使用的模型的启发。*。 图形用户界面可以直观、...
  • Refuge:缓解恐慌发作
    2021-04-27 17:31
    它利用Fitbit api来帮助用户查看他们可能经历了可能引发恐慌发作的刺激的时间。 它还为用户提供了呼吸练习，指导性冥想和播放列表，以帮助降低恐慌发作的强度。 如果他们的生活特别艰难，用户也可以与他们联系，...
  • 在Go中处理恐慌
    2020-08-13 00:47
    cukw6666的博客 在本教程中，我们将研究几种常见的操作可以在Go中产生恐慌的方法，并且还将看到避免这些恐慌的方法。 我们还将使用defer语句以及recover函数来捕获紧急事件，以免它们有可能意外终止正在运行的Go程序。 了解恐慌 ...
  • game:Tortuga Repo恐慌
    2021-04-11 00:50
    游戏Tortuga Repo恐慌
  • 恐慌症-给人类的恐慌信息-Rust开发
    2021-05-27 18:22
    恐慌症对人类的恐慌消息...即使Rust在安全性方面非常出色，但并非不曾听说过访问向量中的错误索引或在某处断言失败的情况。 当错误最终发生时，您可能想知道它。 因此，我们不仅可以在命令行上提供错误消息，还可以创建
  • 最新波动率/恐慌指数VIX数据（exce/bson/json，至2020-07-08）
    2020-07-09 08:12
    波动率/恐慌指数VIX数据（exce/bson/json） - 根据实盘原始股票期权行情数据计算VIX从2015-01至2020-07-08（持续更新中...) - 根据[White Paper Cboe Volatility Index]...
  • 没有解决我的问题, 去提问

悬赏问题

  • ¥15 2024-五一综合模拟赛
  • ¥15 下图接收小电路，谁知道原理
  • ¥15 装 pytorch 的时候出了好多问题，遇到这种情况怎么处理？
  • ¥20 IOS游览器某宝手机网页版自动立即购买JavaScript脚本
  • ¥15 手机接入宽带网线，如何释放宽带全部速度
  • ¥30 关于#r语言#的问题：如何对R语言中mfgarch包中构建的garch-midas模型进行样本内长期波动率预测和样本外长期波动率预测
  • ¥15 ETLCloud 处理json多层级问题
  • ¥15 matlab中使用gurobi时报错
  • ¥15 这个主板怎么能扩出一两个sata口
  • ¥15 不是，这到底错哪儿了😭