> My application work without using valgrind, but when I use valgrind 390 

Thank you for mentioning the version number of valgrind.

with my application, the application crash soon after start:
> 
>  
> 
> ==25545== Process terminating with default action of signal 11
> 
> (SIGSEGV): dumping core
> 
> ==25545==  Access not within mapped region at address 0x86C006000
> 
> ==25545==    at 0x52308C4: _IO_vfscanf (in /lib64/libc-2.4.so)

Please tell us what hardware architecture, and which operating system and 
version,
and which distribution.  Post the output from "uname -a", which gives good 
information.

/lib64 implies a 64-bit machine.  Current glibc on x86_64 boxes is something 
like:
        $ ls -l /lib64/libc-*.so
        -rwxr-xr-x. 1 root root 2108632 Nov 16  2013 /lib64/libc-2.17.so
[that's Fedora 19] so libc-2.4.so must be something else.

> The stack trace seems like the Bug 95667 reported in 2004. I think the bug 
> has been already solved. But why it happened again for me?

Bug 95667 [in 2004, ten years ago] was on x86*,  Because the bug and the fix
are machine-dependent, then perhaps a similar situation arose afterwards
on a different machine architecture.  What architecture *are* you running?


------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to