From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] thread debugging with target gdb
Date: Thu, 20 Sep 2012 14:42:26 +0200 [thread overview]
Message-ID: <20120920144226.70dd0e27@skate> (raw)
In-Reply-To: <zarafa.505b004f.74f2.799ed96c0a00510d@jacal.basystemes.fr>
Dear Thierry Bultel,
On Thu, 20 Sep 2012 13:38:55 +0200, Thierry Bultel wrote:
> Thanks for your help, is there a chance that those fixes get integrated in the mainline ?
Yes, sure. Could you send a proper patch? This way we can keep
attribution, and credit you for the investigation of this problem.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-20 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 15:44 [Buildroot] thread debugging with target gdb Thierry Bultel
2012-09-19 21:04 ` Arnout Vandecappelle
2012-09-19 21:27 ` Thierry Bultel
2012-09-19 21:30 ` Arnout Vandecappelle
2012-09-20 11:38 ` Thierry Bultel
2012-09-20 12:42 ` Thomas Petazzoni [this message]
2012-09-20 15:22 ` [Buildroot] [PATCH] Enables thread debugging with full gdb on target Thierry Bultel
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=20120920144226.70dd0e27@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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