Re: [Valgrind-developers] Bug in VG_(seginfo_sect_kind) ?

[<a.g...@st...>]

> Yes, i've also noticed that it sometimes works (it always works if =20
> you look for type text). For the other types, the .text segment =20
> must overlap the others (in my case i found that the .text in  =20
> vgpreload_core.so overlapped the .bss and .data segments).
>
> Alberto

El 20/03/2007, a las 18:50, Bart Van Assche escribi=F3:

> On 3/20/07, Julian Seward <js...@ac...> wrote:
>
> > The problem is that it only returns the correct segment if the text
> > segment
> > overlaps the other segments, wich is quite unusual. I have =20
> replaced the
> > functions for this and everything seems to work ok on Ubuntu 6.10:
>
> Um, yes.  (!)  My first reaction to the existing implementation is
> that it is completely broken.  Can you send a diff (svn diff -rHEAD
> coregrind/m_debuginfo/debuginfo.c) ?  Thanks.
>
> I use VG_(seginfo_sect_kind)() in drd, and it works at least on X86 =20=

> and AMD64.
>
> Bart Van Assche.
> ----------------------------------------------------------------------=20=

> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =20
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?=20
> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV____________________________=
____=20
> _______________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers