This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

A Question On GDB?


Gentle People:

   I normally use GDB to find Segmentation Fault bugs such as
an uninitialized pointer. Usually I just use the "r" command and
the program runs until it crashes with GDB displaying the source
code file name and line number!

   But in the case shown below GDB dose NOT give me this
this useful information?

    Now the question: How can I find the crash point in the code?

Thanks for the help
Thomas Dineen

Sun5# gdb --args TA_Bench.sun
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.10"...
(gdb) r
Starting program: /net/Dineen-Linux4/home/tdineen/Projects/TA_Bench/TA_Bench.sun

warning: Lowest section in /lib/libpthread.so.1 is .dynamic at 00000074
warning: Lowest section in /lib/libthread.so.1 is .dynamic at 00000074
[New LWP 1]
[New LWP 2]
[LWP 2 exited]
[New LWP 2]
Screen Maximum Size: Width 1920 Height 1200

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb)




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]