os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add a bit more on creating meaningful backtraces with gdb.

Browse source
This commit is contained in:
Joe Marcus Clarke 2006-10-28 04:54:59 +00:00
parent 530a38d725
commit b106c0d7c7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=28956
1 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
en/gnome/docs/bugging.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.27 2006/08/19 21:20:35 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.28 2006/10/14 17:19:11 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: Reporting a Bug">
<!ENTITY % navinclude.gnome "INCLUDE">
]>
@ -68,7 +68,13 @@
<a
href="http://live.gnome.org/GettingTraces">instructions</a>
for more information on obtaining useful back
traces.
traces. In general, though, you can build and
install your port with the following command
to produce binaries that will have useful
debugging symbols: <tt>env CFLAGS="-O -g
-pipe" make STRIP= install</tt> (note: there
is a space between <tt>STRIP=</tt> and
<tt>install</tt>).
<li>If an application produces unexpected behavior,
provide a clear and detailed description, including a
description of the behavior that you were expecting.