|
From: Julian S. <js...@ac...> - 2006-05-10 14:54:54
|
It may be that there is no problem, but just that the 2000000 limit in the assert is too low given the huge size of the object. One way to find out is to increase the limit to number until the assertion no longer fires. Probably worth trying. J On Wednesday 10 May 2006 15:49, Joachim Bauernberger wrote: > Hi Julian, > > we have this in valgrind 3.0.1 and 3.1.1. > Unfortunately this the shared lib is some lib supplied by third-party and I > am unable to give it out :-( > > On 5/5/06, Julian Seward <js...@ac...> wrote: > > Which version of Valgrind is this with? And what CPU ? > > > > Can you make the shared lib available so we can look at what > > the debug info reader is doing? > > > > J > > > > On Friday 05 May 2006 08:25, Joachim Bauernberger wrote: > > > Dear list, > > > > > > we get the following assert when using valgrind: > > > > > > --24267-- Reading syms from > > > /utran/ngrncOmodel/lib/linux/debug/libcschnappi.so (0x1C491000) > > > valgrind: symtab.c:377 (vgModuleLocal_addCfiSI): Assertion 'cfisi->len > > > > > > > > 0 > > > > > && cfisi->len < 2000000' failed > > > > > > could someone tell me how I can interpret this assert and whether it > > > > would > > > > > be safe to remove it? > > > > > > our program uses some shared libs and one of them is extremely big (200 > > > MB+). The assert happens during reading the symbols from this huge > > > > shared > > > > > lib. > > > > > > thanks, > > > joachim > > -- > http://www.bauernberger.de/ > OpenBC: https://www.openbc.com/hp/Joachim_Bauernberger/ > mailto:jo...@ba... > ICQ: 214527045 > Tel/Fax: +(49)-0-89/1588 3874 > HP: +(49)-0-179/674 3611 |