public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org, Michael Snyder <msnyder@vmware.com>,
	Marc Khouzam <marc.khouzam@ericsson.com>,
	Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
	Steven <mqyoung@gmail.com>,
	colyli@gmail.com, Christoph Hellwig <hch@infradead.org>,
	"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: [PATCH] Linux Kernel GDB tracepoint module 2011-02-05
Date: Mon, 07 Feb 2011 09:25:33 -0700	[thread overview]
Message-ID: <m3hbcfzu9u.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTikhfhYjvmvXtjW-Mszpq8d_3Syo=H4zqWe+1hEg__12255.0142732964$1296923928$gmane$org@mail.gmail.com> (Hui Zhu's message of "Sun, 6 Feb 2011 00:37:37 +0800")

>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:

>> We have trouble for this printf is GDB is still not accept the patch
>> that make tracepoint support printf, So if you want use it, you need
>> patch the patch in
>> http://sourceware.org/ml/gdb-patches/2011-02/msg00063.html and build
>> your GDB with yourself.

Thanks, I think this example was helpful.

>> Sometimes, GDB will output some value like:
>> inode has been optimized out of existence.
>> res has been optimized out of existence.
>> That is because value of inode and res is optimized. Linux Kernel is
>> built with -O2 so you will get this trouble sometimes. If you do not
>> care about the speed when you debug the Kernel, you can use the patch
>> for Linux Kernel in

I am curious to know what version of GCC you are using.  IME, the VTA
patches really helped with this problem a lot -- though not completely.
If you are not using a VTA-enabled GCC, you should.  And if you are, I
think bug reports about values that are still optimized out would be
useful.

Tom

       reply	other threads:[~2011-02-07 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikhfhYjvmvXtjW-Mszpq8d_3Syo=H4zqWe+1hEg__12255.0142732964$1296923928$gmane$org@mail.gmail.com>
2011-02-07 16:25 ` Tom Tromey [this message]
2011-02-08 13:23   ` [PATCH] Linux Kernel GDB tracepoint module 2011-02-05 Hui Zhu
2011-02-08 16:00     ` Tom Tromey
2011-02-09 13:25       ` Hui Zhu
2011-02-11 16:29         ` Tom Tromey
2011-02-23  5:32           ` Hui Zhu
2011-02-08 16:27     ` Jan Kratochvil
2011-02-05 16:37 Hui Zhu

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=m3hbcfzu9u.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=colyli@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=mqyoung@gmail.com \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.com \
    --cc=thiago.bauermann@gmail.com \
    /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