From: Jack Bates <ms419@freezone.co.uk>
To: gdb@sourceware.org
Subject: module built with debugging symbols but backtrace: 0x00000050 in ?? ()
Date: Mon, 15 Sep 2008 18:30:00 -0000 [thread overview]
Message-ID: <1221503302.17538.14.camel@ket.lat> (raw)
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
I am trying to debug an Apache module. I compiled it with "-g", however
the first line of my backtrace is:
(gdb) bt
#0 0x00000050 in ?? ()
#1 0xb782f852 in call_get_cert_callback (session=0x81e5550, issuers_dn=0x0,
issuers_dn_length=0, pk_algos=0x0, pk_algos_length=0) at auth_cert.c:430
#2 0xb782fd1b in _gnutls_server_select_cert (session=0x81e5550,
requested_algo=4294967295) at auth_cert.c:1811
[...]
Here is a complete log of compiling and debugging the module:
http://cgi.sfu.ca/~jdbates/tmp/mod-gnutls/200809120/screenlog
I think that the module was built with debugging symbols. Here is the
output from "readelf -w":
http://cgi.sfu.ca/~jdbates/tmp/mod-gnutls/200809150/screenlog
I apologize - I am a gdb novice - my question is: If the module was
built with debugging symbols, why can't I tell from the first line of
the backtrace, where in the module's source code is this segmentation
fault? Why is the first line of the backtrace: 0x00000050 in ?? () -
instead of something more descriptive?
Here is the tread discussing this segmentation fault on
modules@outoforder.cc:
http://lists.outoforder.cc/pipermail/modules/2008-September/000164.html
Thank you! Jack
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-09-15 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 18:30 Jack Bates [this message]
2008-09-15 18:36 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1221503302.17538.14.camel@ket.lat \
--to=ms419@freezone.co.uk \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox