|
From: Thomas L. <tho...@jr...> - 2004-04-13 14:26:43
|
Hi I just updated to valgrind 2.1.1 (previous running version was 2.0) and I encounter a problem (I have never seen it with 2.0). My C program uses a flex/bison parser for reading an input file. Valgrind exits while this input file is read, but without signaling any error. What is really strange to me, is that my program actually parses this input files and prints outputs prooving it does. However, valgrind reports that the "input" in flex scanner failed. I uses valgrind --tool=memcheck -v myprogram Can anybody help in finding why valgrind is detached and reports such an error? Thanks Thomas [many output from my program, reading the input file.] input in flex scanner failed ==20622== ==20622== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 1) --20622-- --20622-- supp: 13 Ugly strchr error in /lib/ld-2.3.2.so ==20622== malloc/free: in use at exit: 31290 bytes in 436 blocks. ==20622== malloc/free: 497 allocs, 61 frees, 34370 bytes allocated. ==20622== --20622-- TT/TC: 0 tc sectors discarded. --20622-- 3240 chainings, 2 unchainings. --20622-- translate: new 4564 (88524 -> 1130025; ratio 127:10) --20622-- discard 1 (23 -> 320; ratio 139:10). --20622-- dispatch: 25500000 jumps (bb entries), of which 8775573 (34%) were unchained. --20622-- 735/6124 major/minor sched events. 4717 tt_fast misses. --20622-- reg-alloc: 1043 t-req-spill, 206269+7427 orig+spill uis, 24275 total-reg-r. --20622-- sanity: 628 cheap, 26 expensive checks. --20622-- ccalls: 21139 C calls, 53% saves+restores avoided (67210 bytes) --20622-- 28497 args, avg 0.85 setup instrs each (8344 bytes) --20622-- 0% clear the stack (63234 bytes) --20622-- 8668 retvals, 28% of reg-reg movs avoided (4806 bytes) |
|
From: David E. <tw...@us...> - 2004-04-13 15:07:00
|
On Tue, 2004-04-13 at 16:25, Thomas Lavergne wrote:
> Hi
> I just updated to valgrind 2.1.1 (previous running version was 2.0) and
> I encounter a problem (I have never seen it with 2.0).
> My C program uses a flex/bison parser for reading an input file.
> Valgrind exits while this input file is read, but without signaling any
> error.
> What is really strange to me, is that my program actually parses this
> input files and prints outputs prooving it does. However, valgrind
> reports that the "input" in flex scanner failed.
>
> I uses valgrind --tool=memcheck -v myprogram
>
> Can anybody help in finding why valgrind is detached and reports such an
> error?
FWIW, I don't think that the message "input in flex scanner failed"
comes from valgrind but from flex or flex-generated code. Just google
for the string.
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sourceforge.net
CalcEm - http://calcem.sourceforge.net
ScummVM - http://scummvm.sourceforge.net
Desquirr - http://desquirr.sourceforge.net
SetiWrapper - http://setiwrapper.sourceforge.net
|
|
From: Nicholas N. <nj...@ca...> - 2004-04-13 15:13:41
|
On Tue, 13 Apr 2004, Thomas Lavergne wrote: > I just updated to valgrind 2.1.1 (previous running version was 2.0) and > I encounter a problem (I have never seen it with 2.0). > My C program uses a flex/bison parser for reading an input file. > Valgrind exits while this input file is read, but without signaling any > error. > What is really strange to me, is that my program actually parses this > input files and prints outputs prooving it does. However, valgrind > reports that the "input" in flex scanner failed. > > I uses valgrind --tool=memcheck -v myprogram > > Can anybody help in finding why valgrind is detached and reports such an > error? > Thanks > Thomas > > [many output from my program, reading the input file.] Sounds like a Valgrind bug. Can you give us the full output from "valgrind -v"? If it's big, can you gzip it and put it on a website? Even better -- can you reduce your program to the smallest size that reproduces the problem and give it to us with sample input? That's the best chance for finding the problem. In the meantime, I guess you can revert to 2.0.0 (actually, it would be interesting to know if 2.1.0 works properly). N |