Re: [Valgrind-users] Valgrind doesn't create readable core dumps

[Ivo R. <ivo...@gm...>]

2015-07-13 19:17 GMT+02:00 Mikhail Baikov <mik...@de...>:

>  Hello.
> Is there a possibility to disable signals handling by valgrind? The core
> will be created by the system and that will solve the problem.
>

This is not an option.
Run of your program (guest) is simulated by Valgrind (host).
Therefore Valgrind itself must create the guest coredump;
operating system can only create coredump of Valgrind (host).

What is your OS and architecture (for example x86/Linux)?

I.


>
> On 07/02/2015 04:11 PM, Mikhail Baikov wrote:
>
> Hello
>
> I've got a problem while reading dumps created by valgrind. I've compiled
> and run this code with valgrind and without it.
> *int main()*
> *{*
> *    const char *str = "segfault";*
> *    *(char *)str = 'a';*
> *    return 1;*
>
> *} *
>
> When I read the system created core dump it's readable
> *Core was generated by `./seg'.*
> *Program terminated with signal 11, Segmentation fault.*
> *#0  0x004006d0 in main () at ./seg.c:4*
>
> When I try to read the core dump created by valgrind, gdb is unable to
> read it
> *warning: Couldn't find general-purpose registers in core file.*
>
> *warning: Could not load shared library symbols for 5 libraries, e.g.
> /bin/valgrind/lib/valgrind/vgpreload_core-mips32-linux.so.*
> *Use the "info sharedlibrary" command to see the complete listing.*
> *Do you need "set solib-search-path" or "set sysroot"?*
> *Core was generated by `'.*
>
> *warning: Couldn't find general-purpose registers in core file.*
> *../../gdb-7.3.1/gdb/frame-unwind.c:133: internal-error:
> frame_unwind_find_by_frame failed*
> *A problem internal to GDB has been detected,*
> *further debugging may prove unreliable.*
>
>