[lkml]   [2002]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectkdb against memory corruption?
    I think i found a case of memory corruption in the backport of
    the linuxconsole-ruby patch to 2.4.19.

    Some parts (not sure which yet) of the tty_struct get
    overwritten. I do not yet know when that happens or how, but i
    intend to find out with kdb and its bph brakepoint feature.

    Unfortunatly my initial attempts to find the instance where the
    memory segment gets corrupted failed. I specified a certain
    address, a length of 4 byte and DATAW as arguments to the bph

    but reading the kdb manpage i get the impression that
    startaddress and length have to match precisly:

    DATAW Enters the kernel debugger when data of length
    length is written to the specified address.

    how can i use this to find the cause of the corruption? Anyone
    done this before? i would want to be alerted whenever anything
    withing a certain memory range gets overwritten.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:29    [W:0.029 / U:31.956 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site