Hello All,
I discovered a "strange" behavior doing a simple operation.
I defined 2 const : one integer and one string. With delve (or other
debugger), I'm able to consult the const integer value but not the const
string value. Delve team explained me that the go compiler doesn't export
symbol
On Thu, May 30, 2024 at 10:34 AM Benoît Marguerie wrote:
> I discovered a "strange" behavior doing a simple operation.
> I defined 2 const : one integer and one string. With delve (or other
> debugger), I'm able to consult the const integer value but not the const
> string value. Delve team exp
Of course!
The code can be really simple like this:
*const myValueStr = "try"const myValueInt = 12*
*func DoSomething() { fmt.Println("Instruction only to put a
breakpoint")}*
and the result with delve:
*(dlv) print %v myValueInt12(dlv) print %v myValueStrCommand failed: could
not
or, in a easier way, a full "copy/paste" example of code:
package main
import "fmt"
const myValueStr = "try"
const myValueInt = 12
func main() {
fmt.Println("Instruction only to put a breakpoint")
}
Le jeudi 30 mai 2024 à 10:53:50 UTC+2, Benoît Marguerie a écrit :
> Of course!
> The code can
Thanks for the response Michael.
> It looks like a Windows minidump (unsurprisingly) can't follow the
relation. A regular goroutine stack trace dump that gets emitted on a
forced exit or crash is able to show both sides of the system stack switch
with a little bit of configuration.
Yeah, that
Hello gophers,
We plan to issue Go 1.22.4 and Go 1.21.11 during US business hours on Tuesday,
June 4.
These minor releases include PRIVATE security fixes to the standard library,
covering the following CVE:
- CVE-2024-24790
Following our security policy, this is the pre-announcement of
Your question should have included more information such as the Go version.
Nonetheless, I don't see how Delve is able to resolve "myValueInt" in your
example. I modified your code to include non-const versions of the symbols:
package main
import "fmt"
const constValueStr = "abc"
const constVa
