[Dune] truncated function names in valgrind

[Oliver Sander]

Hi Andreas,
maybe the following helps:  Start valgrind with the option --db-attach=yes.
Then, when the invalid write occurs, valgrind will ask you whether you want
to attach a debugger to the running process.  Confirm, and you will find
yourself in gdb at the spot where the error occurred.  Then maybe gdb will
tell you the function names.
Best,
Oliver

Am 07.02.2014 11:55, schrieb Andreas Buhr:
> Dear Duners,
> 
> we do have a problem. Maybe someone can help us?
> 
> We have a crashing program. Valgrind tells us it does an invalid write.
> However, Valgrind fails to tell us where exactly this write occurs, as
> Valgrind seems to truncate very long function names and with DUNE, we
> always have very long function names.
> 
> Has anyone experienced this before?
> 
> thanks and best regards,
> Andreas
> 
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 534 bytes
Desc: OpenPGP digital signature
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20140207/9af9301c/attachment.sig>