From: "Alexander Fun" <alexander_fun@gmx.de>
To: help-gcc@gnu.org
Subject: Re: no debugging symbols
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <837mb1$7pt$1@news.rz.uni-karlsruhe.de> (raw)
Message-ID: <19991231222400.QlvsrVqlUmWKI4gTC20AQd9HgUHBCsfql362NGcaCB8@z> (raw)
In-Reply-To: <831ifs$t0g$1@news.rrz.Uni-Koeln.DE>
Boris wrote:
>Don't know what -g3 does but try using -ggdb.
funny:
gcc pimain.cc -ggdb -o debugme
gdb debugme
-> no debugging symbols found
It's no joke. It simply doesn't work.
bye
Alex
next prev parent reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 2:30 Alexander Fun
1999-12-12 17:35 ` Boris
1999-12-15 1:19 ` Alexander Fun [this message]
1999-12-31 22:24 ` Alexander Fun
1999-12-31 22:24 ` Boris
1999-12-31 22:24 ` Alexander Fun
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='837mb1$7pt$1@news.rz.uni-karlsruhe.de' \
--to=alexander_fun@gmx.de \
--cc=help-gcc@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).