1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Is this really possible?

Discussion in 'BlackHat Lounge' started by seoways, Aug 6, 2013.

  1. seoways

    seoways Jr. VIP Jr. VIP Premium Member UnGagged Attendee

    Joined:
    Dec 19, 2009
    Messages:
    4,650
    Likes Received:
    724
    Location:
    Behind you!
    I just come through this thread and excited of how it could have become possible.. imagined of myself.


    [​IMG]

    He joined in Feb 2008.. Lets take, he is giving thanks for every minute in all day(without sleeping) from when he joined.

    60 x 24 x 365 x 5 years = 2628000 - its not even single percent of total number of thanks..

    lets take he was giving thanks in every second..

    60 x 60 x 24 x 365 x 5 = 157680000 -

    so in this case, he should have been giving atleast 30 thanks/second to reach 4294967267 ...

    Note : Pls neglect this. if it has been already discussed here.. :(

    I tried to find the error & guessed this could be the reason for this but dont know exactly.. :) :)

    Code:
    system.byte variable with a value way too big for a byte (2 posts)
    system.byte variable with a value way too big for a byte
    2010/11/12 18:46:21
    
    
    I have noticed this a few times and dont understand it so I thought
    I'd ask.
    When looking at byte values in windbg with sos.dll or psscor2.dll I
    see values in there way above what is allowed.
    
    
    Fields:
    MT Field Offset Type VT
    Attr Value Name
    79333520 4000216 0 System.Byte 1 instance
    4294967267 m_value
    
    
    
    
    I see this a lot, what am I missing? How are numbers like 429496267
    stored in system.byte?
    Answer
    Code:
    Re: system.byte variable with a value way too big for a byte
    2010/11/16 10:40:47
    
    
    On Nov 12, 5:46 pm, JR wrote:
    > I have noticed this a few times and dont understand it so I thought
    > I'd ask.
    > When looking at byte values in windbg with sos.dll or psscor2.dll I
    > see values in there way above what is allowed.
    >
    >     Fields:
    >           MT    Field               Offset   Type VT
    > Attr           Value          Name
    >     79333520  4000216        0          System.Byte  1 instance
    > 4294967267 m_value
    >
    > I see this a lot, what am I missing? How are numbers like 429496267
    > stored in system.byte?
    
    Think about twos-completement arithmetic....
    
    4294967267 = 0xFFFFFFE3
    
    So the byte value of 0xE3 is sign extended to the value you see.
    Roger.



     
  2. dr.Hus

    dr.Hus Regular Member

    Joined:
    Oct 24, 2011
    Messages:
    265
    Likes Received:
    140
    Occupation:
    web design
    Location:
    www
    didnt read whole thread :( sorry
     
  3. redrubies

    redrubies Supreme Member

    Joined:
    Jan 17, 2011
    Messages:
    1,424
    Likes Received:
    2,560
    Location:
    USA
    It's just a glitch.