Hi Ian,
You are correct. The following test case is failing. I commented out the
code to make sure whether my analysis is correct or not. Definitely, you
people are experts. What could be the best fix for this issue? If you can
help then that is really helpful.
=== RUN TestCallbackPanicLoop
sig
On Tue, Apr 4, 2023 at 9:20 PM mariappan balraj
wrote:
>
> In my test case, I have tried, Go-->C-->Go->panic() only.
You can run a bunch of cgo tests by running "go test" in the directory
$GOROOT/misc/cgo/test.
Ian
> On Wed, Apr 5, 2023 at 3:35 AM Ian Lance Taylor wrote:
>>
>> On Mon, Apr 3,
Hi Ian,
In my test case, I have tried, Go-->C-->Go->panic() only.
On Wed, Apr 5, 2023 at 3:35 AM Ian Lance Taylor wrote:
> On Mon, Apr 3, 2023 at 9:26 PM mariappan balraj
> wrote:
> >
> > Hi Kurtis Rader,
> >
> > Thanks for your response. I am working on it. I will quickly share it.
> Before t
Sorry. Forgot to share go environment.
root@soomohan:/home/soomohan/mbalraj/test_hb2# go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/root/g
On Tue, Apr 4, 2023 at 3:30 PM robert engels wrote:
> Unfortunately, I am on OSX - and Go doesn’t appear to generate a core dump
> on panic despite the GOTRACEBACK setting.
>
> That being said, the stack-traces look ok to me. See attached.
>
Since I also use macOS (aka "OS X") I investigated why
Unfortunately, I am on OSX - and Go doesn’t appear to generate a core dump on panic despite the GOTRACEBACK setting.That being said, the stack-traces look ok to me. See attached.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe fro
On Mon, Apr 3, 2023 at 9:26 PM mariappan balraj
wrote:
>
> Hi Kurtis Rader,
>
> Thanks for your response. I am working on it. I will quickly share it. Before
> that one more update. I have commented the below two lines. Now from the
> core, I am able to see the correct stack trace.
>
> 326 func
Hi Robert,
I have published the test case on github. Please find the links. Please let
me know if you need any information. I am ready to provide and support.
https://github.com/MariappanBalraj/test_cgo_panic
https://github.com/MariappanBalraj/test_cgo_panic.git
https://github.com/MariappanBalra
Hi Kurtis Rader,
Thanks for your response. I am working on it. I will quickly share it.
Before that one more update. I have commented the below two lines. Now from
the core, I am able to see the correct stack trace.
326 func unwindm(restore *bool) {
327 if *restore {
328 /
You have not done what Robert suggested. That is, "I would start by
publishing a small reproducible test case on github that fully compiles
that demonstrates the issue." It may not be practical to do so. However,
providing the source code for a small reproducible test case will make it
infinitely e
Hi Robert,
Eagerly waiting for your help. Some further update.
I have set a break point at line number 332 by using dlv, noted the value
of shced.sp. Once line number 332 is executed, reset the value of sched.sp
by using set command in dlv. In this case, I am getting the proper trace.
326 func
I would start by publishing a small reproducible test case on github that fully
compiles that demonstrates the issue.
> On Apr 2, 2023, at 10:59 PM, mariappan balraj
> wrote:
>
>
> Hello Go Experts,
>
> It is good if someone can help on this?
>
> Best Regards
> Mariappan
>> On Sat, Apr 1
Hello Go Experts,
It is good if someone can help on this?
Best Regards
Mariappan
On Sat, Apr 1, 2023 at 7:45 AM mariappan balraj
wrote:
> Hello Go experts,
>
> Could someone please help to resolve this issue?
>
> Best Regards
> Mariappan
>
> On Thu, Mar 30, 2023 at 2:52 PM mariappan balraj <
>
13 matches
Mail list logo