UTC+2 schreef Bernd Fix:
On 8/8/23 18:16, Kurtis Rader wrote:
Did you also recompile the plugin with the new Go toolchain? It's a
requirement of plugin support that the main program and all plugins be
compiled with the same toolchain.
Yes, the loading program and the module were both com
ersion" (I remember seeing that once) - but
certainly not a panic in a regular expression parser.
On Tue, Aug 8, 2023 at 11:12 AM Bernd Fix wrote:
After switching from go1.20.7 to go1.21.0 one of my applications
compiles without warnings or errors, but fails at run-time with the
follo
After switching from go1.20.7 to go1.21.0 one of my applications
compiles without warnings or errors, but fails at run-time with the
following panic when loading a plugin:
panic: regexp: Compile(`^([\w./]+)/((?:\w+)|[*])(.+)?$`): error parsing
regexp: invalid escape sequence: `\w`
goroutine
No, p.Data is not nil - and the panic does not happen in the Key()
method, but in the code from my first email.>Y<
On 9/26/22 07:08, Andrew Harris wrote:
could p.Data could be nil here?
On Monday, September 26, 2022 at 12:03:20 AM UTC-7 Bernd Fix wrote:
On 9/25/22 19:05, Kurtis
On 9/25/22 19:05, Kurtis Rader wrote:
Insufficient information. Show us the panic
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x49388d]
goroutine 100037 [running]:
leatea/core.(*ForwardTable).Learn(0xcb
On 9/25/22 19:06, 'Axel Wagner' via golang-nuts wrote:
Another possibility is someone trying (and failing) to use unsafe to speed
things up in a []byte/string conversion and accidentally converts a
nil-slice.
No unsafe in my own code, but I use a third-party library ("sdlcanvas")
for renderi
On 9/25/22 18:35, Jason Phillips wrote:
Have your tried building and running your application with the race
detector enabled[1]? You may have a data race.
Thanks for the advice; that is possible although I have checked that
access to all unsafe types like maps and arrays is controlled by
mute
Hi folks,
I am using go1.19.1 for development and see a strange panic ("invalid
memory address") in an application; the panic is definitely not
triggered by a nil dereference (the object in question is a string):
key = peer.Key()
entry, ok := tbl.recs[key]
The panic happens in the seco
