|
From: Alessandro B. <a.b...@ev...> - 2010-08-12 07:49:21
|
Hi,
how can I see the "Vg_DebugMsg" on my console output when
executing a valgrind istance?
Which option I have to do? Where I can find this information?
Thanks.
|
|
From: WAROQUIERS P. <phi...@eu...> - 2010-08-12 08:07:45
|
You can give one or more -v arguments and/or one or mode -d arguments.
This will produce more verbose valgrind output and/or produce debug
output.
There are also other debug switches, which you can find by :
valgrind --help-debug
Philippe
________________________________
From: Alessandro Biasci [mailto:a.b...@ev...]
Sent: Thursday 12 August 2010 09:49
To: val...@li...
Subject: [Valgrind-users] Debug message
Hi,
how can I see the "Vg_DebugMsg" on my console output when
executing a valgrind istance?
Which option I have to do? Where I can find this information?
Thanks.
____
This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.
Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.
Any views expressed in this message are those of the sender. |
|
From: Julian S. <js...@ac...> - 2010-08-12 08:55:50
|
You can also send output to a network socket (eg, --log-socket=127.0.0.1:1500) and have the valgrind-listener program listen on the socket. This is really really useful (at least I think so :-) but nobody seems to know it exists. J On Thursday, August 12, 2010, WAROQUIERS Philippe wrote: > You can give one or more -v arguments and/or one or mode -d arguments. > This will produce more verbose valgrind output and/or produce debug > output. > > There are also other debug switches, which you can find by : > valgrind --help-debug > > Philippe > > ________________________________ > > From: Alessandro Biasci [mailto:a.b...@ev...] > Sent: Thursday 12 August 2010 09:49 > To: val...@li... > Subject: [Valgrind-users] Debug message > > > Hi, > > how can I see the "Vg_DebugMsg" on my console output when > executing a valgrind istance? > > Which option I have to do? Where I can find this information? > > Thanks. > > > > > ____ > > This message and any files transmitted with it are legally privileged and > intended for the sole use of the individual(s) or entity to whom they are > addressed. If you are not the intended recipient, please notify the sender > by reply and delete the message and any attachments from your system. Any > unauthorised use or disclosure of the content of this message is strictly > prohibited and may be unlawful. > Nothing in this e-mail message amounts to a contractual or legal commitment > on the part of EUROCONTROL, unless it is confirmed by appropriately signed > hard copy. > Any views expressed in this message are those of the sender. |
|
From: WAROQUIERS P. <phi...@eu...> - 2010-08-12 09:21:29
|
>From: Julian Seward [mailto:js...@ac...] >You can also send output to a network socket (eg, >--log-socket=127.0.0.1:1500) >and have the valgrind-listener program listen on the socket. This is >really really useful (at least I think so :-) but nobody seems to know >it exists. > >J Effectively, having a way to avoid mixing VG output with program output is interesting. I replicated this idea as part of the gdbserver patch: I have hooked up on the "log output sink" to allow gdb to display the VG output. However, the output_log_sink does not work for debug. >From what I can see, VG_(debugLog) always goes to stderr. Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Alessandro B. <a.b...@ev...> - 2010-08-12 09:29:02
|
Thanks for help. With the debug message actives I see the .sdata and .sbss sections are listed in my ELF file but have 0 size. This cause an exit of read_elf_debug_info() function in coregrind/m_debuginfo/readelf.c file. I don't understand this. If section is mentioned but size is 0 the function exits with error code doesn't skip it and continues to check the other. Make this skip valgrind works in my ppc board. Thanks again. On 12/08/2010 11:22, WAROQUIERS Philippe wrote: > >> From: Julian Seward [mailto:js...@ac...] >> You can also send output to a network socket (eg, >> --log-socket=127.0.0.1:1500) >> and have the valgrind-listener program listen on the socket. This is >> really really useful (at least I think so :-) but nobody seems to know >> it exists. >> >> J >> > Effectively, having a way to avoid mixing VG output with program output > is > interesting. > I replicated this idea as part of the gdbserver patch: I have hooked up > on the "log output sink" to allow gdb to display the VG output. > > However, the output_log_sink does not work for debug. > From what I can see, VG_(debugLog) always goes to stderr. > > Philippe > > > ____ > > This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. > > Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. > > Any views expressed in this message are those of the sender. > |
|
From: Julian S. <js...@ac...> - 2010-08-12 09:32:02
|
On Thursday, August 12, 2010, WAROQUIERS Philippe wrote: > >From: Julian Seward [mailto:js...@ac...] > >You can also send output to a network socket (eg, > >--log-socket=127.0.0.1:1500) > >and have the valgrind-listener program listen on the socket. This is > >really really useful (at least I think so :-) but nobody seems to know > >it exists. > > > >J > > Effectively, having a way to avoid mixing VG output with program output > is > interesting. > I replicated this idea as part of the gdbserver patch: I have hooked up > on the "log output sink" to allow gdb to display the VG output. > > However, the output_log_sink does not work for debug. > From what I can see, VG_(debugLog) always goes to stderr. VG_(debugLog) is a different mechanism. It is intended for low level debugging, so that it can work and print output even when no other parts of the system work. This has proved very valuable in the past. Hence it is deliberately very simple and is hardwired to stderr. J > > Philippe > > > ____ > > This message and any files transmitted with it are legally privileged and > intended for the sole use of the individual(s) or entity to whom they are > addressed. If you are not the intended recipient, please notify the sender > by reply and delete the message and any attachments from your system. Any > unauthorised use or disclosure of the content of this message is strictly > prohibited and may be unlawful. > Nothing in this e-mail message amounts to a contractual or legal commitment > on the part of EUROCONTROL, unless it is confirmed by appropriately signed > hard copy. > Any views expressed in this message are those of the sender. |