All:

I am working on a pilot go/cgo project for a database driver.  For one of 
my C functions called by go, I chose a generic, unfortunate name 
connect().  My program  kept dumping core on Linux.  I did some tracing and 
found out that my function connect() was being called twice even though I 
called it just once.  I renamed the function as myconnect() and the problem 
went away.  Here is an nm output after the fact:

0000000000000277 T _cgo_c208fc38ae96_Cfunc_myconnect
0000000000000634 T myconnect

Is this expected?  Is there a general pattern to protect against this?

With regards,

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to