Return to Answer

The same thing is discussed a bit deeper here .

The same thing is discussed a bit deeper here .

To arrive to your _init function just continue execution. This will stop once again in the intended place.

According to information about shared libraries, it stopped first time in address area of libc.so , which looks like also has _init function, which caused gdb to set this breakpoint there too (see breakpoint definition at the end of the listing).

To arrive to your _init function just continue execution. This will stop once again in the intended place.

According to information about shared libraries, it stopped first time in address area of libc.so, which looks like also has _init function, which caused gdb to set this breakpoint there too (see breakpoint definition at the end of the listing).

Good luck.

If you want to set a breakpoint in your specific address, you can use

 b *address

notation. If you want to set a breakpoint on a specific function from specific source file you can use something like

(gdb) break test.c:call1

The same thing is discussed a bit deeper here .

Good luck.