Rebasing
process of modifying data based on one reference to another
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/370 discontinuous 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; This eliminates a certain class of buffer overflow security problems related to improper checking of null-terminated strings, common in the C programming 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 daylight saving time (DST) rebasing tool TZMOVE.EXE contained in Microsoft Exchange and Outlook uses to recalculate and reschedule appointment dates that are affected by DST.
See also
Relocation (computing)
Position-independent code
Portable Executable (PE)
High memory area (HMA)
Dynamic dead-code elimination
Further reading
Levine, John R. (2000) [October 1999]. Linkers and Loaders. The Morgan Kaufmann Series in Software Engineering and Programming (1 ed.).
“Rebasing” enters the record as process of modifying data based on one reference to another. Crown Archives preserves that source wording while asking what Rebasing, process and modifying can confirm, complicate or overturn.
Why this record matters
“Rebasing” is worth following because a concise public description often conceals a longer documentary argument. Here, Rebasing, process and modifying provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jul 24, 2026. The linked authority identifier is Q7301613. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2000 and 1999.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Rebasing”, its source revision and the description used here.
- Expand the search: follow Rebasing primary sources, Rebasing archive and Rebasing research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Rebasing”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Rebasing” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.