Dangling Pointer between C and Go

Shintaro Kaneko — Mon, 22 May 2023 04:10:00 +0000

In this post, I'm going to tell you about how to handle Dangling Pointer and understand the difference of behavior between C and Go.

Dangling Pointer

Dangling point is a pointer that doesn’t point to a valid object of the appropriate type. It doesn’t happen in modern programming language such as Go, Rust, etc but it usually happens in three scenarios:

De-allocation: If a pointer is pointing to a memory location of an object, but the object either has been deleted or de-allocated.
Function Call: If a pointer is pointing to a local variable of a function and the function call gets over.
Variable goes out of scope: If a pointer is pointing to a variable that has gone out of scope.

The pointer of these scenarios is known as a dangling pointer.

Dangling pointers can lead to undefined behavior in a program, including program crashes, data corruption, or memory leaks. To avoid this, we should always set pointers to null after they are freed, and avoid using pointers that point to local variables outside the scope of their function.

Garbage Collector

Go has the Garbage Collector, and all variables that refer to an object are deleted, the object will be automatically deleted by system. However, C doesn’t have the Garbage Collector, which means programmers must handle allocated objects by themselves. If they use malloc to allocate memory dynamically, they have to take care of the memory’s scope and living period until the memory is valid.

C code

In terms of the following code, the variable r of the new_rect function is expected to be used outside the function.

#include <stdio.h>

// rect represents the coordinate of rectangle.
struct rect {
    float x;
    float y;
};

// new_rect returns a reference of a variable of rect.
struct rect *new_rect(float x, float y) {
    struct rect r = {
        .x =  x,
        .y =  y,
    };
    return &r;
}

int main(int argc, char* argv[]) {
    struct rect *rp = new_rect(2.0, 3.0);
    printf("address = %p\\n", rp);
    printf(" (x, y) = (%f, %f)\\n", rp->x, rp->y);
    return 0;
}
// Output:
// address = 0x16d1c3140
//  (x, y) = (3021218960012547179075862528.00, 0.00)

The variable r that exists in the new_rect function is deleted when the function call ends. It turns out, the function retuns an address that has already been invalid. The pointer rp points to the invalid local address and the dangling pointer error occurs.

Go code

However, in the following Go code, the variable rp in the main function points to a memory address of the variable r that is defined in the NewRect function and has NOT been deleted. So, dangling pointer error doesn’t occur.

package main

import "fmt"

// Rect represents the coordinate of rectangle.
type Rect struct {
    X float32
    Y float32
}

// NewRect returns a reference of a variable of Rect.
func NewRect(x, y float32) *Rect {
    r := Rect{
        X: x,
        Y: y,
    }
    return &r
}

func main() {
    rp := NewRect(2.0, 3.0)
    fmt.Printf("address = %p\\n", rp)
    fmt.Printf(" (x, y) = (%f, %f)\\n", rp.X, rp.Y)
}
// Output:
// address = 0x1400011c008
//  (x, y) = (1.20, 3.40)

That’s all there is.

SSH: Remove identified keys by hostname

Shintaro Kaneko — Mon, 09 Mar 2020 13:24:48 +0000

Failed to connect to the host via ssh.

Have you ever seen such a error which is "Failed to connect to the host via ssh." on your terminal when connecting a host via ssh. It should be happened if known_hosts file is taken a wrong identified keys belonging to the host.

$ ssh foobar@foobar.com
Failed to connect to the host via ssh.

-R hostname

To clear the problem you may take away the identified keys with ssh-keygen command.

$ man ssh-keygen

...
-R hostname
        Removes all keys belonging to hostname from a known_hosts file.  This option is useful to
        delete hashed hosts (see the -H option above).
...

Use f option to specify a known_hosts files.

$ ssh-keygen -f ~/.ssh/known_hosts -R foobar.com
# No more
# rm -f ~/.ssh/known_hosts

That's it! :)

Troubleshooting `ld: library not found for -lssl'

Shintaro Kaneko — Mon, 24 Feb 2020 04:52:15 +0000

Trouble

linking shared-object mysql2/mysql2.bundle                                                              
ld: library not found for -lssl                                                                         
clang: error: linker command failed with exit code 1 (use -v to see invocation)                                             
make: *** [mysql2.bundle] Error 1                                                                       

make failed, exit code 2

I got the error during executing gem install mysql2. It seems that the linkable library path is not configured correctly on Mojave.

Shooting

Invoking the command with LIBRARY_PATH to be able to find out the openssl library explicitly.

$ LIBRARY_PATH=$LIBRARY_PATH:/usr/local/opt/openssl/lib gem install mysql2

That's all. 😎

DEV Community: Shintaro Kaneko