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

2015-07-28 Thread Mikhail Baikov
Hello I see that gdb can't find general purpose registers. /warning: Couldn't find general-purpose registers in core file.// /Maybe valgrind adds these registers with some wrong offset? On 07/14/2015 04:52 PM, Mikhail Baikov wrote: Architecture is mipsel. OS is Linux. the output of uname -a is

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

2015-07-14 Thread Mikhail Baikov
Architecture is mipsel. OS is Linux. the output of uname -a is Linux 192.168.23.55 3.3.8-3.3 #1 SMP Fri Jul 10 10:11:31 MSK 2015 mips GNU/Linux On 07/13/2015 08:28 PM, Ivo Raisr wrote: 2015-07-13 19:17 GMT+02:00 Mikhail Baikov mailto:mikhail.bai...@dev.zodiac.tv>>: Hello. Is ther

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

2015-07-13 Thread Ivo Raisr
2015-07-13 19:17 GMT+02:00 Mikhail Baikov : > 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 Valgrin

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

2015-07-13 Thread Mikhail Baikov
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. 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-users] Valgrind doesn't create readable core dumps

2015-07-02 Thread Mikhail Baikov
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 /