panic: TypeInfo already exists for exported.Account
goroutine 1 [running]:
how to handle these unexpected behaviour?
The best way were to not let it happen at all.
Write your code in a way that panics don’t occur…
Though you can use
recover to “catch” a panic. Wont give you much when you do it in
main though, as it will exit anyway (at the point when the
defered function is called, then
main is already left…
You can not just restart your program or continue after the
catch block as you would in many other languages.
how can I know what is the error(in which file it is) and how to remove it.
Learn how to read the trace.
From what you have posted, I’d take a look at line 313 of
github.com/blockkungpao/fbc/app.go. Its not available (publicly) on GitHub though…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.