identifying cause of segfault with gdb?

[Amit Bhatia]

Hello.
 Is it possible to identify the source of a segmentation fault(which is most
probably being caused due to memory access of place which I am not allowed
to) using gdb?
 I wish to know the name of the erring call or line no in the method where
this could be happening.
 I am using g++ 3.2 on redhat 9.0, and do compile with -c -pg flag.(and
finally make libmyown.a and then link it to the compiled test program).

thanks,
amit.