Process of modifying data based on one reference to another
This article may lack focus or may be about more than one topic. Please help improve this article, possibly by splitting the article and/or by introducing a disambiguation page, or discuss this issue on the talk page.(September 2016)
This article is about computing activities. For the use of a new base for the CPI, see consumer price index.
In computing, rebasing is the process of modifying data based on one reference to another. It can be one of the following:
Shared libraries
Rebasing is the process of creating a shared library image in such a way that it is guaranteed to use virtual memory without conflicting with any other shared libraries loadable in the system.
IBM VM/370discontinuous saved segments (DCSS) were an early example of this technique, though not called rebasing. The technique is used extensively on Win32 platforms to avoid the overhead of address relocation of system DLLs by the loader.
Some security extensions to Linux/x86 use rebasing to force the use of code addresses below 0x00ffffff in order to introduce a 0x00 byte into all code pointers;[citation needed] This eliminates a certain class of buffer overflow security problems related to improper checking of null-terminated strings, common in the Cprogramming language.
Other uses
Rebasing is the act of moving changesets to a different branch when using a revision control system or in some systems, by synchronizing a branch with the originating branch by merging all new changes in the latter to the former. For example, Git and Darcs do this (but Darcs extends the concept and calls it "patch commutation").
The mechanism that the Microsoft Exchange or Outlookdaylight saving time (DST) rebasing tool TZMOVE.EXE uses to recalculate and reschedule appointment dates that are affected by DST.
