Live data from Hacker News

Viewing profile — ice799

ice799

HN member
Joined
Wed, May 07, 2008, 5:59 PM UTC
HN karma
1,136
Public activity
72 items

About ice799

@joedamato github.com/ice799 joe at packagecloud.io

Recent public activity

  1. story
  2. comment
    Comment #9408533

    I built https://packagecloud.io to help make creating, hosting, and installing APT (and other) repositories easier. Check it out :D

  3. story
  4. comment
  5. comment
    Comment #8032377

    Check out my above comment and feel free to ping me via email or twitter. Would love to get more detailed feedback from you and maybe try to change your mind!

  6. comment
    Comment #8032343

    Hi! Just for fun: man reprepro and search for 'corrupt' :) You can use all your normal tools to upgrade, install, and remove packages as you normally would. So, for, Debian-based s…

  7. story
  8. comment
    Comment #5669836

    I thought it was pretty crazy that a tweak to prevent XFree86 from breaking on 64bit systems + support for the ELF small code execution model would later result in pthread_create o…

  9. story
  10. story
  11. comment
  12. comment
    Comment #4190042

    search the page for linux and check the tags at the bottom. says linux a few times bro.

  13. story
  14. comment
    Comment #3472950

    hi. linux does have this. you just strip the debug symbols out (and put them somewhere safe). then write a .gnu_debuglink section to the stripped ELF binary with a CRC that matches…

  15. comment
    Comment #2734950

    the gzip bug mentioned did not segfault. it simply corrupted the gzip file in memory. not that selective son. imma talk the way i talk and dont give a fuck if you like it or not.

  16. comment
    Comment #2733633

    You are totally missing the point, bro. The question really is: how much data corruption is occurring that _does not_ cause world ending segfaults? THAT is what you need to worry a…

  17. comment
    Comment #2732104

    registers are scanned, too. the bug is not that the ref is in a register. the bug is that there are no refs anywhere. not on the stack and not in any register.

  18. story
  19. story
  20. story
  21. comment
    Comment #1533430

    thanks man. i've also updated the graphs on my blog.

  22. comment
    Comment #1533426

    done, refresh page and you should see em.

  23. comment
    Comment #1533424

    grossly exaggerated? bro, i gave the raw numbers in a table above the graph. if i were trying to lie i wouldn't have given the numbers. i took the graphs as-is from goog docs and p…

  24. comment
    Comment #1533395

    Spilling has nothing to do with this. GCC has the chance to pick another GPR that is caller saved but instead picks a callee saved register. This decision increases the size of lib…

  25. comment
    Comment #1533366

    building the code in the bug report as a 64bit binary and various system information: http://gist.github.com/483494 and testing harness, scripts to build it, and to run it: http://…