This is the mail archive of the
mailing list for the GDB project.
Re: Need help with a backtrace
- To: gdb at sourceware dot cygnus dot com, mschalit at pacbell dot net
- Subject: Re: Need help with a backtrace
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: Thu, 15 Feb 2001 12:47:56 -0800
> In general, when a backtrace gives a really meager output
> like the following:
> and that's all the lines it output, am I supposed to
> put breakpoints into my convert program to see when
> it makes a call to a libc function?
That depends on what your goal is.
If your goal is to debug your gnome app and send useful reports to
the gnome people -- then you put breakpoints in your convert program.
You could also build your program with "-static", which brings in a
static copy of all the library functions that you use. That will make
gdb behave a lot better.
If your goal is to help improve gdb -- then you write up a detailed
the whole source code of a program that demonstrates the bug
the exact command line you used to build
"gcc --version" (or the equivalent with the compiler you use)
"ldd a.out" on your executable (or the Unixware equivalent)
ls -l on each shared library used
a typescript showing your whole gdb session
Writing a detailed gdb bug report is a task in its own right.
Then you post the bug report, and see if someone will work on it.
If no one responds in a couple of days, you can check the MAINTAINERS
file and e-mail the SCO/Unixware maintainers and ask them the status of
your bug report.
Michael Elizabeth Chastain
"love without fear"