|
From: Mikhail B. <mik...@de...> - 2015-07-02 13:48:49
|
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./
Can you help me with this?
P.S.
cpu model: Broadcom BMIPS5000 V1.1 FPU V0.1
valgrind-3.10.1
--
Sincerely
Mikhail Baikov
|
|
From: Mikhail B. <mik...@de...> - 2015-07-13 17:17:13
|
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 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./
>
> Can you help me with this?
> P.S.
> cpu model: Broadcom BMIPS5000 V1.1 FPU V0.1
> valgrind-3.10.1
>
> --
> Sincerely
> Mikhail Baikov
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
>
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
--
Sincerely
Mikhail Baikov
|
|
From: Ivo R. <ivo...@gm...> - 2015-07-13 17:28:46
|
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.*
>
>
|
|
From: Mikhail B. <mik...@de...> - 2015-07-14 13:52:30
|
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
> <mik...@de... <mailto: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./
>
>
--
Sincerely
Mikhail Baikov
|
|
From: Mikhail B. <mik...@de...> - 2015-07-28 14:00:23
|
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
> 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
>> <mik...@de... <mailto: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./
>>
>>
>
> --
> Sincerely
> Mikhail Baikov
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
>
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
--
Sincerely
Mikhail Baikov
|