Skip to content

Instantly share code, notes, and snippets.

@danslo

danslo/4

Created June 20, 2014 10:43
Show Gist options
  • Save danslo/b4d416e854b54fff13bb to your computer and use it in GitHub Desktop.
Save danslo/b4d416e854b54fff13bb to your computer and use it in GitHub Desktop.
Download ZIP
Raw
4
==20393== 8 bytes in 1 blocks are definitely lost in loss record 88 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 89 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 90 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 91 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 92 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 93 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 94 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 95 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 96 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 97 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 98 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 99 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 100 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 101 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 102 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 103 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 104 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 105 of 1,153
==20393== 8 bytes in 1 blocks are definitely lost in loss record 106 of 1,153
==20393== 16 bytes in 1 blocks are possibly lost in loss record 231 of 1,153
==20393== 16 bytes in 1 blocks are possibly lost in loss record 232 of 1,153
==20393== 16 bytes in 1 blocks are definitely lost in loss record 233 of 1,153
==20393== 16 bytes in 2 blocks are definitely lost in loss record 234 of 1,153
==20393== 16 bytes in 2 blocks are definitely lost in loss record 235 of 1,153
==20393== 16 bytes in 2 blocks are definitely lost in loss record 236 of 1,153
==20393== 16 bytes in 2 blocks are definitely lost in loss record 237 of 1,153
==20393== 16 bytes in 2 blocks are definitely lost in loss record 238 of 1,153
==20393== 24 bytes in 3 blocks are definitely lost in loss record 247 of 1,153
==20393== 26 bytes in 1 blocks are possibly lost in loss record 248 of 1,153
==20393== 26 bytes in 1 blocks are possibly lost in loss record 249 of 1,153
==20393== 26 bytes in 1 blocks are possibly lost in loss record 250 of 1,153
==20393== 26 bytes in 1 blocks are possibly lost in loss record 251 of 1,153
==20393== 26 bytes in 1 blocks are possibly lost in loss record 252 of 1,153
==20393== 29 bytes in 1 blocks are possibly lost in loss record 253 of 1,153
==20393== 29 bytes in 1 blocks are possibly lost in loss record 254 of 1,153
==20393== 29 bytes in 1 blocks are possibly lost in loss record 255 of 1,153
==20393== 30 bytes in 1 blocks are possibly lost in loss record 256 of 1,153
==20393== 30 bytes in 1 blocks are possibly lost in loss record 257 of 1,153
==20393== 30 bytes in 1 blocks are possibly lost in loss record 258 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 279 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 280 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 281 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 282 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 283 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 284 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 285 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 286 of 1,153
==20393== 32 bytes in 1 blocks are possibly lost in loss record 287 of 1,153
==20393== 32 bytes in 2 blocks are possibly lost in loss record 288 of 1,153
==20393== 33 bytes in 1 blocks are possibly lost in loss record 289 of 1,153
==20393== 34 bytes in 1 blocks are possibly lost in loss record 290 of 1,153
==20393== 34 bytes in 1 blocks are possibly lost in loss record 291 of 1,153
==20393== 34 bytes in 1 blocks are possibly lost in loss record 292 of 1,153
==20393== 34 bytes in 1 blocks are possibly lost in loss record 293 of 1,153
==20393== 34 bytes in 1 blocks are possibly lost in loss record 294 of 1,153
==20393== 35 bytes in 1 blocks are possibly lost in loss record 295 of 1,153
==20393== 36 bytes in 1 blocks are possibly lost in loss record 296 of 1,153
==20393== 36 bytes in 1 blocks are possibly lost in loss record 297 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 298 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 299 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 300 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 301 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 302 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 303 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 304 of 1,153
==20393== 37 bytes in 1 blocks are possibly lost in loss record 305 of 1,153
==20393== 38 bytes in 1 blocks are possibly lost in loss record 306 of 1,153
==20393== 39 bytes in 1 blocks are possibly lost in loss record 307 of 1,153
==20393== 39 bytes in 1 blocks are possibly lost in loss record 308 of 1,153
==20393== 39 bytes in 1 blocks are possibly lost in loss record 309 of 1,153
==20393== 40 bytes in 1 blocks are possibly lost in loss record 322 of 1,153
==20393== 40 bytes in 1 blocks are possibly lost in loss record 323 of 1,153
==20393== 40 bytes in 2 blocks are possibly lost in loss record 324 of 1,153
==20393== 40 bytes in 2 blocks are possibly lost in loss record 325 of 1,153
==20393== 40 bytes in 5 blocks are definitely lost in loss record 326 of 1,153
==20393== 40 bytes in 5 blocks are definitely lost in loss record 327 of 1,153
==20393== 41 bytes in 1 blocks are possibly lost in loss record 328 of 1,153
==20393== 41 bytes in 1 blocks are possibly lost in loss record 329 of 1,153
==20393== 41 bytes in 1 blocks are possibly lost in loss record 330 of 1,153
==20393== 42 bytes in 1 blocks are possibly lost in loss record 331 of 1,153
==20393== 42 bytes in 1 blocks are possibly lost in loss record 332 of 1,153
==20393== 42 bytes in 1 blocks are possibly lost in loss record 333 of 1,153
==20393== 42 bytes in 1 blocks are possibly lost in loss record 334 of 1,153
==20393== 43 bytes in 1 blocks are possibly lost in loss record 335 of 1,153
==20393== 43 bytes in 1 blocks are possibly lost in loss record 336 of 1,153
==20393== 43 bytes in 1 blocks are possibly lost in loss record 337 of 1,153
==20393== 43 bytes in 1 blocks are possibly lost in loss record 338 of 1,153
==20393== 43 bytes in 1 blocks are possibly lost in loss record 339 of 1,153
==20393== 43 bytes in 1 blocks are possibly lost in loss record 340 of 1,153
==20393== 43 bytes in 1 blocks are possibly lost in loss record 341 of 1,153
==20393== 44 bytes in 1 blocks are possibly lost in loss record 342 of 1,153
==20393== 44 bytes in 1 blocks are possibly lost in loss record 343 of 1,153
==20393== 44 bytes in 1 blocks are possibly lost in loss record 344 of 1,153
==20393== 44 bytes in 1 blocks are possibly lost in loss record 345 of 1,153
==20393== 44 bytes in 1 blocks are possibly lost in loss record 346 of 1,153
==20393== 45 bytes in 1 blocks are possibly lost in loss record 347 of 1,153
==20393== 45 bytes in 1 blocks are possibly lost in loss record 348 of 1,153
==20393== 45 bytes in 1 blocks are possibly lost in loss record 349 of 1,153
==20393== 45 bytes in 1 blocks are possibly lost in loss record 350 of 1,153
==20393== 45 bytes in 1 blocks are possibly lost in loss record 351 of 1,153
==20393== 45 bytes in 1 blocks are possibly lost in loss record 352 of 1,153
==20393== 45 bytes in 1 blocks are possibly lost in loss record 353 of 1,153
==20393== 46 bytes in 1 blocks are possibly lost in loss record 354 of 1,153
==20393== 46 bytes in 1 blocks are possibly lost in loss record 355 of 1,153
==20393== 46 bytes in 1 blocks are possibly lost in loss record 356 of 1,153
==20393== 46 bytes in 1 blocks are possibly lost in loss record 357 of 1,153
==20393== 46 bytes in 1 blocks are possibly lost in loss record 358 of 1,153
==20393== 46 bytes in 1 blocks are possibly lost in loss record 359 of 1,153
==20393== 46 bytes in 1 blocks are possibly lost in loss record 360 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 361 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 362 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 363 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 364 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 365 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 366 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 367 of 1,153
==20393== 47 bytes in 1 blocks are possibly lost in loss record 368 of 1,153
==20393== 48 bytes in 1 blocks are possibly lost in loss record 448 of 1,153
==20393== 48 bytes in 1 blocks are possibly lost in loss record 449 of 1,153
==20393== 48 bytes in 1 blocks are possibly lost in loss record 450 of 1,153
==20393== 48 bytes in 1 blocks are possibly lost in loss record 451 of 1,153
==20393== 48 bytes in 3 blocks are possibly lost in loss record 452 of 1,153
==20393== 48 bytes in 6 blocks are definitely lost in loss record 453 of 1,153
==20393== 49 bytes in 1 blocks are possibly lost in loss record 454 of 1,153
==20393== 49 bytes in 1 blocks are possibly lost in loss record 455 of 1,153
==20393== 50 bytes in 1 blocks are possibly lost in loss record 456 of 1,153
==20393== 52 bytes in 1 blocks are possibly lost in loss record 457 of 1,153
==20393== 53 bytes in 1 blocks are possibly lost in loss record 458 of 1,153
==20393== 56 bytes in 1 blocks are possibly lost in loss record 498 of 1,153
==20393== 57 bytes in 1 blocks are possibly lost in loss record 499 of 1,153
==20393== 62 bytes in 1 blocks are possibly lost in loss record 500 of 1,153
==20393== 65 bytes in 1 blocks are possibly lost in loss record 519 of 1,153
==20393== 72 bytes in 1 blocks are possibly lost in loss record 631 of 1,153
==20393== 75 bytes in 1 blocks are possibly lost in loss record 632 of 1,153
==20393== 81 bytes in 1 blocks are possibly lost in loss record 641 of 1,153
==20393== 152 bytes in 1 blocks are possibly lost in loss record 749 of 1,153
==20393== 155 bytes in 1 blocks are possibly lost in loss record 750 of 1,153
==20393== 156 bytes in 1 blocks are possibly lost in loss record 751 of 1,153
==20393== 156 bytes in 1 blocks are possibly lost in loss record 752 of 1,153
==20393== 169 bytes in 1 blocks are possibly lost in loss record 761 of 1,153
==20393== 176 bytes in 1 blocks are possibly lost in loss record 768 of 1,153
==20393== 200 bytes in 1 blocks are possibly lost in loss record 779 of 1,153
==20393== 211 bytes in 2 blocks are possibly lost in loss record 781 of 1,153
==20393== 224 bytes in 13 blocks are possibly lost in loss record 786 of 1,153
==20393== 240 bytes in 3 blocks are possibly lost in loss record 810 of 1,153
==20393== 270 bytes in 3 blocks are possibly lost in loss record 838 of 1,153
==20393== 336 bytes in 20 blocks are possibly lost in loss record 863 of 1,153
==20393== 352 bytes in 44 blocks are definitely lost in loss record 867 of 1,153
==20393== 360 bytes in 45 blocks are definitely lost in loss record 872 of 1,153
==20393== 592 bytes in 74 blocks are definitely lost in loss record 927 of 1,153
==20393== 1,320 bytes in 165 blocks are definitely lost in loss record 999 of 1,153
==20393== 2,048 bytes in 102 blocks are possibly lost in loss record 1,029 of 1,153
==20393== 13,851 bytes in 243 blocks are possibly lost in loss record 1,101 of 1,153
==20393== 23,313 bytes in 239 blocks are possibly lost in loss record 1,120 of 1,153
==20393== 25,703 bytes in 239 blocks are possibly lost in loss record 1,121 of 1,153
==20393== definitely lost: 3,024 bytes in 377 blocks
==20393== indirectly lost: 0 bytes in 0 blocks
==20393== possibly lost: 71,726 bytes in 982 blocks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment