From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Lassi Niemistö" <lassi.niemisto@wapice.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] PowerPC hardware watchpoints unstable with GDB and Xenomai
Date: Mon, 13 Jun 2016 17:20:34 +0200 [thread overview]
Message-ID: <20160613152034.GK898@hermes.click-hack.org> (raw)
In-Reply-To: <d7f1e0d09cba4c14a5e0e20d168a2141@EDB2.wapice.localdomain>
On Mon, Jun 13, 2016 at 03:14:05PM +0000, Lassi Niemistö wrote:
> > Whether or not you should contact the gdb mailing list is simple: if you get the issue without Xenomai, then it is a
> > gdb issue, if you get the issue only with Xenomai, then it is a Xenomai issue, and there is no reason to bother the
> > gdb mailing list.
>
> Well, I had no idea which side contains the Xenomai support and I wished the GDB guys to provide some debugging hints. But if you see it most probably as a Xenomai issue, let's not cross-post it then.
>
>
> > Xenomai 2.6.1 is pretty old, a lot of things have been fixed since then, including issues with gdb. So, do you get the same issue with Xenomai 2.6.4?
>
> I will find out if we have the possibility of trying the version
> update with sensible effort.
The update should be painless: the two versions belong to the same
branch, they are ABI compatible. This means that you do not even
need to recompile your applications, you simply need to compile the
new xenomai version. Also, recompiling the kernel support should be
enough.
>
> A thought: I have been getting "warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available." at GDB startup, but ignored it this far as the threading has worked just fine.. Might this have anything to do with my issue, and does anyone know how to get rid of the message on Xenomai? I know how to specify the library for GDB, but which one should be the correct for Xenomai?
No idea, I always debugged threaded programs with libthread_db.so,
and it has to come from the toolchain used to compile the target
gdb/gdbserver. And if using gdbserver, the cross-gdb running on host
and the gdbserver running on target should have the same version too.
--
Gilles.
https://click-hack.org
prev parent reply other threads:[~2016-06-13 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 10:33 [Xenomai] A fix to few generic issues in rttcp stack Matti Suominen
2016-03-31 10:44 ` Gilles Chanteperdrix
2016-03-31 16:22 ` Gilles Chanteperdrix
2016-04-01 9:36 ` Matti Suominen
2016-04-01 10:40 ` Gilles Chanteperdrix
2016-04-03 19:09 ` Gilles Chanteperdrix
2016-04-30 6:49 ` Gilles Chanteperdrix
2016-05-02 6:32 ` Matti Suominen
2016-05-02 7:10 ` Gilles Chanteperdrix
2016-05-03 4:54 ` Matti Suominen
2016-05-03 5:55 ` Gilles Chanteperdrix
2016-06-13 14:01 ` [Xenomai] PowerPC hardware watchpoints unstable with GDB and Xenomai Lassi Niemistö
2016-06-13 14:30 ` Gilles Chanteperdrix
2016-06-13 15:14 ` Lassi Niemistö
2016-06-13 15:20 ` Gilles Chanteperdrix [this message]
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=20160613152034.GK898@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lassi.niemisto@wapice.com \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.