[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
[an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]![]() |
![]() |
![]() |
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
![]() |
![]() |
![]() |
2009/10/5 Atte André Jensen <sslug@sslug>: > 1) Hvad findes der af alternativer til 1.000.000 printf-statements? Jeg > forestiller mig noget, evt med GUI, jeg kan køre mit segfaultende program > igennem og så få at vide hvor det crasher og evt lidt mere om hvorfor. compiler med -g (jeg går ud fra at du bruger g++) og kør den gennem valgrind (`valgrind foo`, hvor foo er din binary). den fanger dine hukommelsesfejl. -- regards Bjørn Hartfelt
![]() |
![]() |
![]() |
||||||||||||
|
||||||||||||||
![]() | ||||||||||||||
|
||||||||||||||
![]() |
![]() |
![]() |