Just filed https://bugs.kde.org/show_bug.cgi?id=245535
--kcc

On Tue, Apr 20, 2010 at 6:01 PM, Konstantin Serebryany
<[email protected]> wrote:
>
>
> On Tue, Apr 20, 2010 at 2:18 PM, Stefano Sabatini <[email protected]>
> wrote:
>>
>> Hi all,
>>
>> I'm currently using valgrind-3.5.0-Debian.
>>
>> I see in the commentary:
>> ...
>> ==7197==    by 0x80688A3: XYZ::Foo::Bar() (FooBar.cxx:361)
>> ==7197==    by 0x4326435: PThread::PX_ThreadStart(void*)
>> (tlibthrd.cxx:1341)
>> ==7197==    by 0x4042584: start_thread (pthread_create.c:300)
>> ==7197==    by 0x47CA29D: clone (clone.S:130)
>>
>> Since I'm using emacs, which has support for the
>> path/to/file:line_num syntax, I'd like valgrind to print the complete
>> pathname and allow me to jump to the source with just one click.
>>
>> So I wonder if it would be possible for example for valgrind to print:
>> ==7197==    by 0x80688A3: XYZ::Foo::Bar()
>> (/home/stefano/src/foobar-proj/libfoobar/FooBar.cxx:361)
>>
>> Is it currently already implemented? (from the reading of the docs it
>> seems no)
>
> Yes, in regular (non-xml) mode valgrind does not print full path names
> (dunno why).
> I usually run patched valgrind which does:
> ===================================================================
> --- coregrind/m_debuginfo/debuginfo.c   (revision 11094)
> +++ coregrind/m_debuginfo/debuginfo.c   (working copy)
> @@ -1851,12 +1851,14 @@
>           APPEND("???");
>        }
>        if (know_srcloc) {
> -         APPEND(" (");
> +         APPEND(" ");
> +         APPEND(buf_dirname);
> +         APPEND("/");
>           APPEND(buf_srcloc);
>           APPEND(":");
>           VG_(sprintf)(ibuf,"%d",lineno);
>           APPEND(ibuf);
> -         APPEND(")");
> +         //APPEND(")");
>        } else if (know_objname) {
>           APPEND(" (in ");
>           APPEND(buf_obj);
>
>
>
>>
>> Should I file a feat request on bugzilla?
>>
>> Regards.
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Valgrind-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to