I took the pain of scrolling through out that thing and your issue is
related to linking of libstdc++.so.6.0.18 sections
I think your issue relates to this bug:
http://sourceware.org/bugzilla/show_bug.cgi?id=12851.
A series of patches are proposed to fix that.
R
On 06/07/2013 11:40 AM, rahul wrote:
Hi,
I hope attached logs will help in understanding this problem, please
let me know if attaching logs are permitted here or not, as this is
first time I am running into some Issue.
Regards,
On Fri, Jun 7, 2013 at 2:34 PM, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote:
On 7 June 2013 09:49, Riccardo Manfrin wrote:
On 06/07/2013 08:14 AM, rahul wrote:
looks like, no one is interested in giving clue about the problem.
Regards,
I'm sorry I don't know anything about systemmap, but still, trying to read
through your posts, I could not find the information required to understand
your issue. When you report about an error it should be your responsibility
to
- provide precise information about your environment to replicate the issue
(all I saw was Fedora 15; I'm into bare-metal so I would for instance
indicate the target and cpu (and would probably become offtopic ;)) but I
guess there is a plethora of information elements you can provide aside
that, even though you compile on top of an OS),
- provide the *command* issuing the error (and I haven't seen it yet around)
and
- provide the generated log *from that command on* (not at a random point
after that).
You were asked 2 times if there were previous error; you did add some extra
log but I suspect there's more to see before that.
R
And don't sound so ungrateful if you don't get the answers you're looking for!
You won't make anyone want to help with comments like "looks like
noone is interested" when people are giving up their own time to help
you.
