This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH V4 5/9] New probe type: DTrace USDT probes.
- From: Joel Brobecker <brobecker at adacore dot com>
- To: "Jose E. Marchesi" <jose dot marchesi at oracle dot com>
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>, gdb-patches at sourceware dot org
- Date: Tue, 31 Mar 2015 11:47:27 -0700
- Subject: Re: [PATCH V4 5/9] New probe type: DTrace USDT probes.
- Authentication-results: sourceware.org; auth=none
- References: <1422874968-382-1-git-send-email-jose dot marchesi at oracle dot com> <1422874968-382-6-git-send-email-jose dot marchesi at oracle dot com> <87r3tp722i dot fsf at redhat dot com> <20150325191418 dot GA32233 at adacore dot com> <87bnjfraq1 dot fsf at oracle dot com> <20150326175028 dot GA13867 at adacore dot com> <87y4mdjcie dot fsf at oracle dot com>
> I just tried the following in a x86-solaris machine, using todays git
> In this system DTrace generates little-endian DOF data, and it looks
> like GDB handles it just fine. I still think the problem you observed
> is related to endianness, but I cannot be sure without looking at the
> contents of the DOF program embedded in your binaries...
Sorry, I was going to send you an email this morning, and then got
carried away by other duties... :-(
I've been able to reproduce the problem, but when I checked again
with a non-AdaCore debugger, the problem went away. I'm not really
sure whether this indicates whether this is an issue caused by
some of our local changes, or whether this is just a latent bug
that gets triggered by those local changes. Either way, it felt like
I would have no choice but to get more familiar with how those probes
work. The problem is that I'm short on time again. But, if you have
any kind of document describing how this data is laid out in the
binary, I'm very interested.
Sorry I waited so long before getting back to you!