search

bitwiseworks / libc

LIBC Next (kLIBC fork)
9 stars 4 forks source link

Unable to launch PM app from libc-dependent shell (dash, etc.) #85

Open LewisR opened 4 years ago

LewisR commented 4 years ago

From a dash session, attempting to launch EPM fails, silently returning to a prompt.

Some shells have workarounds for this (latest bash 3.2.0.8, etc.). Steve suggests that this might be best addressed in libc directly and that KO's enhanced execve() should drop in without much hassle, thus making this a universal fix for all libc-dependent shells.

Use case:

Setting editor-cmd in %HOME%.subversion\config to epm.exe with dash set as default shell will fail to launch EPM to edit a commit message.

SilvanScherrer commented 2 years ago

I wonder to which enhanced execve() you point. Any link?

LewisR commented 2 years ago

Steve as referring to KO's mksh.exe and ksh.exe, where he implemented a private execve(). Perhaps have a look at https://github.com/komh/mksh-os2/blob/master/exec.c.

LewisR commented 2 years ago

Or, rather, https://github.com/komh/mksh-os2/blob/master/os2.c.

SilvanScherrer commented 2 years ago

Btw you refer to latest bash as 3.2.0.8 this is avery old Version. We have 5.0.11 since months

LewisR commented 2 years ago

Realize that I opened this ticket in July of 2020, using dash, not bash. I have dash 0.5.10.2 installed, which I believe was the same one I had previously. I can confirm that:

# epm <Enter>

simply returns to a prompt.

SilvanScherrer commented 2 years ago

Your sentence on first comment: Some shells have workarounds for this (latest bash 3.2.0.8, etc.). 

SilvanScherrer commented 2 years ago

i can confirm latest bash has the same issue.