Bug 351692

Created attachment 94197 [details]
This core was created by valgrind

I've got a problem while reading core dumps created by valgrind. I compiled code that causes segfault and ran the output binary with valgrind and without it (setting ulimit -c unlimited).
The code is
int main()
{
    const char *str = "segfault";
    *(char *)str = 'a';
    return 1;
}

Core dumps were created in both cases, one by valgrind and another by system
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.

One of the important things is that valgrind was compiled for mipsel. I see that gdb can't find general-purpose registers in core file so maybe valgrind compiled for mipsel CPU adds these registers with some wrong offset?