For this type of thing I'd recommend a debugger.
--
Aram Hăvărneanu
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
On Thu, Oct 31, 2019 at 11:44 PM Xiangdong JI wrote:
>
> Thanks Ian, having difficulty figuring out how to print a pointer using
> write1, could you please shed a light? Thanks.
You have to do something like (untested)
var buf [20]byte
b := itoa(buf[:], uint64(uintptr(ptrToPrint)))
Thanks Ian, having difficulty figuring out how to print a pointer using
write1, could you please shed a light? Thanks.
On Friday, November 1, 2019 at 2:00:04 PM UTC+8, Ian Lance Taylor wrote:
>
> On Thu, Oct 31, 2019 at 5:10 AM Xiangdong JI > wrote:
> >
> > seeking utilities for diagnosing
On Thu, Oct 31, 2019 at 5:10 AM Xiangdong JI wrote:
>
> seeking utilities for diagnosing some 'nosplit' runtime functions. Thanks a
> lot.
b := []byte("my debug message\n")
write1(2, [0], len(b))
Ian
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
seeking utilities for diagnosing some 'nosplit' runtime functions. Thanks a
lot.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
