|
From: Naveen K. <g_n...@ya...> - 2005-08-04 22:40:16
|
Hi all, I am getting the following error valgrind: dwarf.c:1750 (read_encoded_Addr): the 'impossible' happened. ==274148== at 0xB00166CC: ??? Is this something to do with the debug info present in the elf file or is it due to something else ? Thanks Naveen __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Tom H. <to...@co...> - 2005-08-04 22:47:36
|
In message <200...@we...>
Naveen Kumar <g_n...@ya...> wrote:
> I am getting the following error
>
> valgrind: dwarf.c:1750 (read_encoded_Addr): the
> 'impossible' happened.
> ==274148== at 0xB00166CC: ???
>
>
> Is this something to do with the debug info present in
> the elf file or is it due to something else ?
Yes, it means the DWARF debugging information is using an address
encoding that valgrind doesn't currently handle - gcc doesn't seem
to use it and it was hard to implement so I didn't bother.
It's a data segment relative address, so the problem is working out
the address of the data segment for the object in question.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Nicholas N. <nj...@cs...> - 2005-08-04 23:25:42
|
On Thu, 4 Aug 2005, Naveen Kumar wrote:
> Hi all,
> I am getting the following error
>
> valgrind: dwarf.c:1750 (read_encoded_Addr): the
> 'impossible' happened.
> ==274148== at 0xB00166CC: ???
>
>
> Is this something to do with the debug info present in
> the elf file or is it due to something else ?
The code says:
case DW_EH_PE_datarel:
vg_assert(0);
base = /* data base address */ 0;
break;
It looks like this is a case that hasn't been implemented properly yet in
the CIE reader. You could try commenting it out and see what happens.
Julian might have more comments.
N
|