Closed Bug 25006 Opened 26 years ago Closed 18 years ago

Patching Linux binary results in unrunnable file

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P5)

Other
Linux
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jimmykenlee, Assigned: dveditz)

Details

(Whiteboard: [xpibug])

Build: 12/24/99 (LINUX) 1. From http://jimbob/trigger2.html, enter and trigger http://jimbob/jars/f_addunixpatch.xpi 2. Then trigger http://jimbob/jars/f_unixpatch.xpi to apply the patch 3. Change to the /unixpatch subdirectory that is created to check the patched file //////////////////////////////////////////////////////////////////////////////// // f_addunixpatch.js // // Acceptance test // • Adds a component to set up Patch() from f_unixpatch.xpi // • This test investigates patching a unix binary file // // ~ XPInstall QA // January 24, 2000 // //////////////////////////////////////////////////////////////////////////////// var regName = "f_unixpatch"; var jarSrc = "test_exe"; var vi = "1.1.1.1"; startInstall("Functional: f_addunixpatch", "f_unixpatch", vi, 0); f = getFolder("Program", "unixpatch"); err = addFile(regName, vi, jarSrc, f, jarSrc, true); logComment("addFile returns = " + err); //////////////////////////////////////////////////////////////////////////////// // f_unixpatch.js // // Functional test // • Patches a binary file test_exe; the new file will output text to the // screen x times // // test_exe x // // Dependency // • f_addunixpatch.xpi should be triggered to set up target file for // patching // // ~ XPInstall QA // January 24, 2000 // //////////////////////////////////////////////////////////////////////////////// var regName = "f_unixpatch"; var jarSrc = "test_exe_param.gdf"; var vi = "2.2.2.2"; startInstall("Functional: f_unixpatch", "f_unixpatch", vi, 0); f = getFolder("Program", "unixpatch"); err = patch(regName, vi, jarSrc, f, "test_exe", true); logComment("patch returns= " + err); RESULT: The Version Registry updates properly. The Install.log appears accurate. The patched binary file now has permissions of -rw-r--r--. Manually changing the permissions to restore x allows for executing the file as expected. EXPECTED RESULT: The file permissions should not lose the executable permission. The original file installed from f_addunixpatch.xpi has permissions -rwxr-xr-x. The permissions of the gdf patch from f_unixpatch.xpi are -rwxrwxrwx.
Moving [PP] to pp in keyword field. and adding patch keyword
Keywords: patch, pp
Summary: [PP]Patch: Patching Linux binary results in changed file permissions → Patching Linux binary results in changed file permissions
Target Milestone: M15
we should make the resulting file has the same permission of the original file. marking as REMIND.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → REMIND
Target Milestone: M15 → M17
I am proposing that REMIND be removed for this bug. The problem is not merely a matter of permissions. The patch fails, and I cannot confirm if it is directly related to permissions or not. Sorry for the lack of clarification. For the case originally described, manually restoring permissions will result in dumping core if the binary is executed. There is no known workaround if this bug is not fixed.
Status: RESOLVED → REOPENED
Resolution: REMIND → ---
see if we can fix for PR3
Target Milestone: M17 → M18
Parcelling out Cathleen's bugs
Assignee: cathleen → sgehani
Status: REOPENED → NEW
Status: NEW → ASSIGNED
No "patch" has been submitted for this bug. It is about the "patching" feature in the XPInstall engine. Removing erroneous inclusion of "patch" keyword.
Keywords: patch
nominating for nsbeta3 by QA. Binary patching still crashes. This is the only patching solution available for linux binaries.
Keywords: nsbeta3
nsbeta3-: Patching is not a priority for this release. Changing the summary to something more vague due to comments that the permissions is not the only problem with the patch.
Summary: Patching Linux binary results in changed file permissions → Patching Linux binary results in unrunnable file
Whiteboard: [nsbeta3-]
Priority: P3 → P1
Resetting target field for missed milestones
Target Milestone: M18 → ---
nominating nsbeta1, removing obsolete nsbeta3 keyword and CC's
Keywords: nsbeta3 → nsbeta1
Whiteboard: [nsbeta3-]
I think I have the other patching bugs at the moment.
Assignee: sgehani → dveditz
Status: ASSIGNED → NEW
Whiteboard: [xpibug]
Moz 0.9 tasks
Target Milestone: --- → mozilla0.9
Priority: P1 → P5
Keywords: nsbeta1, pp → nsbeta1-
Target Milestone: mozilla0.9 → ---
Keywords: nsbeta1- → nsBranch
I recommend nsbranch- for this patching bug.
marking nsbranch- per PDT triage
Keywords: nsbranch → nsbranch-
Blocks: 107067
Keywords: nsbranch-
No longer blocks: 107067
nsbeta1-. No patching this time around.
Status: NEW → ASSIGNED
The xpinstall script engine has been removed from the trunk, bugs in it are obsolete.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 18 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.