From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: debugging enabled? (was Re: KGDB command line options not working for kernel 2.6.32)
Date: Mon, 27 Jun 2011 21:51:53 +0700 [thread overview]
Message-ID: <BANLkTi=ee7A-O-2LYuvCdFM_wfs7z2mgew@mail.gmail.com> (raw)
>I have one question in this context. Should we disable optimization when >building the kernel when we wish to enable kgdb or should we leave it intact.
Whenever possible, yes...disable optimization.... -O option and -g in
gcc don't play nicely together according to my experience. The DWARF
info will be somewhat fuzzed or even "corrupted"....so it might point
to wrong source line etc
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next reply other threads:[~2011-06-27 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 14:51 Mulyadi Santosa [this message]
2011-06-27 18:40 ` debugging enabled? (was Re: KGDB command line options not working for kernel 2.6.32) Spiro Trikaliotis
2011-06-28 1:51 ` Mulyadi Santosa
2011-06-28 6:25 ` Prabhu nath
2011-06-28 10:11 ` Mulyadi Santosa
2011-06-28 17:41 ` Dave Hylands
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='BANLkTi=ee7A-O-2LYuvCdFM_wfs7z2mgew@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).