redox issueshttps://gitlab.redox-os.org/redox-os/redox/-/issues2023-08-31T13:26:30Zhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1400make qemu vga=no is not working anymore2023-08-31T13:26:30ZRibbonmake qemu vga=no is not working anymore`make qemu vga=no` is not working after the VirtIO MRs, someone has the same error?
- OS - Pop OS 22.04
- CPU - Intel® Core™ i3-1005G1
[qemu-vga-no.log](/uploads/aaccb267a245d23996f2c004368a3e90/qemu-vga-no.log)`make qemu vga=no` is not working after the VirtIO MRs, someone has the same error?
- OS - Pop OS 22.04
- CPU - Intel® Core™ i3-1005G1
[qemu-vga-no.log](/uploads/aaccb267a245d23996f2c004368a3e90/qemu-vga-no.log)https://gitlab.redox-os.org/redox-os/redox/-/issues/1376ion boot on qemu fails with redoxfs panic2023-07-10T11:07:07ZIvan Tanion boot on qemu fails with redoxfs panic![image](/uploads/ab8ceefbcf047f649a84e60961089199/image.png)![image](/uploads/ab8ceefbcf047f649a84e60961089199/image.png)https://gitlab.redox-os.org/redox-os/redox/-/issues/1370libc: wait() causing abort2023-06-26T18:20:53ZRon Williamslibc: wait() causing abortOccasionally, Ion will abort, sometimes with the message "wait() should either return Ok or panic", which is coming from `rust/library/std/src/sys/unix/process/process_unix.rs`
This is random behavior, and causes the Terminal window to e...Occasionally, Ion will abort, sometimes with the message "wait() should either return Ok or panic", which is coming from `rust/library/std/src/sys/unix/process/process_unix.rs`
This is random behavior, and causes the Terminal window to exit. The error is only visible on the console.https://gitlab.redox-os.org/redox-os/redox/-/issues/903Filenames with colons2023-06-13T04:42:48ZJeremy SollerFilenames with colons*Created by: dasisdormax*
As the colon separates the scheme and the reference (filename), things may behave weird or unexpected when working with files that include it in their filename.
While (i guess) not many programs need to work w...*Created by: dasisdormax*
As the colon separates the scheme and the reference (filename), things may behave weird or unexpected when working with files that include it in their filename.
While (i guess) not many programs need to work with filenames with colons, they should be able to work without having to write different code for Redox/non-Redox operating systems.
### Examples
**Example 1**:
- Boot into Redox, open a shell as user and execute
~~~
touch file:/home/user/:
ls
~~~
- ls will fail (trying to get information about the root of the unnamed scheme) outputting just:
~~~
error: permission denied
~~~
**Example 2**:
- Boot into Redox, open a shell as user and execute
~~~
touch file:/home/user/file:
ls -l
~~~
- ls will output the file information about the root directory of the file scheme instead of the file "file:" within the current working directory:
~~~
-rw------- 1000 1000 [...] LICENSE
-rw------- 1000 1000 [...] README.md
drwxr-xr-x 0 0 [...] file:
~~~
**Build information (for both examples)**:
self-built redox
rustc 1.17.0-nightly (3da40237e 2017-03-24)
git revision 24f080b4fca8555b15de89272697dfb8062226dd (March 25)
### What can we do?
**Currently working:**
For relative filenames, you can prepend the current working directory to everything. If you use `ls $PWD` in the examples above, everything works as expected as $PWD already contains the scheme.
**Suggestion, not working today:**
For paths including slashes (such as the absolute "/home/user/:" or the relative "./:"), it is clear (at least to me) that the program wants to access that file, not a scheme called "/home/user/" or "./". These variants would mean the same on both Redox and non-Redox operating systems.
This does assume though that scheme names can not contain slashes. If it is intended to support such scheme names, this would obviously not be possible.
### Discuss!https://gitlab.redox-os.org/redox-os/redox/-/issues/806Can't close the "Browser"2023-06-13T04:42:46ZJeremy SollerCan't close the "Browser"*Created by: PeterJCLaw*
**Reproduction**:
* Boot the 0.0.5 iso image
* Log in as either user
* Click the web browser from the task bar at the bottom
* This launches the browser, but due to networking issues I'm having never manage...*Created by: PeterJCLaw*
**Reproduction**:
* Boot the 0.0.5 iso image
* Log in as either user
* Click the web browser from the task bar at the bottom
* This launches the browser, but due to networking issues I'm having never manages to show a page -- instead it just shows a black window.
* Attempt to close the browser
![dead-browser](https://cloud.githubusercontent.com/assets/336212/21594484/10ac78c8-d11b-11e6-86b5-333ef64d4731.png)
**Expected behavior**:
The browser window should close.
**Actual behavior**:
The browser window remains.
**Misc**:
I'm running VirtualBox 5.1.12 on Ubuntu 16.04.
I'm using the settings from https://github.com/redox-os/redox/issues/764, including the boot-device ordering trick mentioned by @vocivvy. The OS doesn't seem to ever get a valid DHCP address, and the browser never gets past showing a black page,
The bug above also reproduces by not presenting the OS with a network card at all and then launching the browser.https://gitlab.redox-os.org/redox-os/redox/-/issues/805Logging out doesn't close "Editor"2023-06-13T04:42:45ZJeremy SollerLogging out doesn't close "Editor"*Created by: PeterJCLaw*
**Reproduction**:
* Boot the 0.0.5 iso image
* Log in as either user
* Click the file browser from the task bar at the bottom
* Click the README.md file in the launched file browser (which launches it in the Edi...*Created by: PeterJCLaw*
**Reproduction**:
* Boot the 0.0.5 iso image
* Log in as either user
* Click the file browser from the task bar at the bottom
* Click the README.md file in the launched file browser (which launches it in the Editor)
* Click Logout in the bottom right
**Expected behavior**:
When logging out, all open programs should close.
**Actual behavior**:
All other programs close as expected, though the Editor instance remains live and can be interacted with even while the Orbital login dialog is shown.
![editor-over-login](https://cloud.githubusercontent.com/assets/336212/21593984/5403ff8e-d115-11e6-9163-9d2a427a5a93.png)
**Misc**:
I'm using VirtualBox 5.1.12 on Ubuntu 16.04.
To get Redox to boot into Orbital I've had to not provide a network card, though I'm assuming that that's unrelated to the above.https://gitlab.redox-os.org/redox-os/redox/-/issues/855Memory leak or memory statistic bug2023-06-13T04:35:59ZJeremy SollerMemory leak or memory statistic bug*Created by: gdf8gdn8*
**Reproduction**:
Download redox-os/livesd.iso from github v0.0.9
Run qemu with
> qemu-system-x86_64 -boot d -cdrom "livedisk.iso" -smp 1 -m 512
Login
Open terminal. Run free several times
![image](https:...*Created by: gdf8gdn8*
**Reproduction**:
Download redox-os/livesd.iso from github v0.0.9
Run qemu with
> qemu-system-x86_64 -boot d -cdrom "livedisk.iso" -smp 1 -m 512
Login
Open terminal. Run free several times
![image](https://cloud.githubusercontent.com/assets/496932/23272151/774a7fa0-f9fa-11e6-98a4-678dfe09b767.png)
**Expected behavior**:
No leaks
**Actual behavior**:
Produce leaks
**Build information**:
redox-os: Precompiled redox-os/livesd.iso from github v0.0.9
OS: MacOS 16.4.0
same result under Linuxhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1197Compile Redox with Docker on macOS 10.12 (Sierra)2023-06-13T04:26:01ZMichael HölzlCompile Redox with Docker on macOS 10.12 (Sierra)First i tried to compile Redox on macOS but i can't build the toolchain.
```
Compiling compiler_builtins v0.1.0 (https://github.com/rust-lang-nursery/compiler-builtins.git#2a2f6d96)
Compiling platform v0.1.0 (file:///Users/michaelho...First i tried to compile Redox on macOS but i can't build the toolchain.
```
Compiling compiler_builtins v0.1.0 (https://github.com/rust-lang-nursery/compiler-builtins.git#2a2f6d96)
Compiling platform v0.1.0 (file:///Users/michaelhoelzl/libc/build/cross/relibc/src/platform)
Compiling itoa v0.4.1
error[E0432]: unresolved import `sys`
--> src/platform/src/lib.rs:15:9
|
15 | pub use sys::*;
| ^^^ Maybe a missing `extern crate sys;`?
error[E0423]: expected function, found macro `write`
--> src/platform/src/lib.rs:89:9
|
89 | write(self.0, buf)
| ^^^^^ did you mean `write!(...)`?
help: possible better candidates are found in other modules, you can import them into scope
|
15 | use core::fmt::write;
|
15 | use core::ptr::write;
|
error[E0425]: cannot find function `read` in this scope
--> src/platform/src/lib.rs:111:9
|
111 | read(self.0, buf)
| ^^^^ not found in this scope
help: possible candidate is found in another module, you can import it into scope
|
15 | use core::ptr::read;
|
Compiling quote v0.3.15
error: aborting due to 3 previous errors
You've got a few errors: E0423, E0425, E0432
If you want more information on an error, try using "rustc --explain E0423"
error: Could not compile `platform`.
warning: build failed, waiting for other jobs to finish...
error: build failed
make: *** [target/debug/libc.a] Error 101
Michaels-MacBook-Pro-2:libc michaelhoelzl$
```
Then i tried to use the Docker image and now i get this error.
```
Already up-to-date.
cook - smith fetch
Already up-to-date.
cook - userutils fetch
Already up-to-date.
cook - uutils fetch
Already up-to-date.
cook - zerod fetch
Already up-to-date.
fusermount -u build/filesystem/ || true
fusermount: entry for /Users/michaelhoelzl/redox/build/filesystem not found in /etc/mtab
rm -rf build/filesystem.bin build/filesystem.bin.partial build/filesystem/
dd if=/dev/zero of=build/filesystem.bin.partial bs=1048576 count=256
256+0 records in
256+0 records out
268435456 bytes (268 MB, 256 MiB) copied, 2.11981 s, 127 MB/s
cargo run --manifest-path redoxfs/Cargo.toml --release --bin redoxfs-mkfs build/filesystem.bin.partial
Finished release [optimized] target(s) in 1.04s
Running `redoxfs/target/release/redoxfs-mkfs build/filesystem.bin.partial`
redoxfs-mkfs: created filesystem on build/filesystem.bin.partial, reserved 0 blocks, size 268 MB, uuid c036f8cd-ec60-4817-a0a8-889b87bfb015
mkdir -p build/filesystem/
cargo build --manifest-path redoxfs/Cargo.toml --release --bin redoxfs
Finished release [optimized] target(s) in 1.25s
cargo run --manifest-path redoxfs/Cargo.toml --release --bin redoxfs -- build/filesystem.bin.partial build/filesystem/
Finished release [optimized] target(s) in 0.45s
Running `redoxfs/target/release/redoxfs build/filesystem.bin.partial build/filesystem/`
redoxfs: opening build/filesystem.bin.partial
redoxfs: opened filesystem on build/filesystem.bin.partial with uuid c036f8cd-ec60-4817-a0a8-889b87bfb015
fuse: failed to open /dev/fuse: Permission denied
redoxfs: failed to mount build/filesystem.bin.partial to build/filesystem/: Permission denied (os error 13)
redoxfs: not able to mount path build/filesystem.bin.partial
mk/filesystem.mk:2: recipe for target 'build/filesystem.bin' failed
make: *** [build/filesystem.bin] Error 1
Michaels-MacBook-Pro-2:redox michaelhoelzl$
```Jeremy SollerJeremy Sollerhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1289Start of netsurf-fb leads to Invalid opcode fault2023-06-13T02:47:56ZphidegStart of netsurf-fb leads to Invalid opcode fault- [X] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
Starting the browser leads to following error:
```
Invalid opcode fault
RFLAG: 0000000000010206
CS: 00000000000...- [X] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
Starting the browser leads to following error:
```
Invalid opcode fault
RFLAG: 0000000000010206
CS: 0000000000000023
RIP: 00000000008D9EB0
RAX: 00000180000FF403
RCX: 0000000000000000
RDX: 0000000000000001
RDI: 0000000000000002
RSI: 0000000000CA39FA
R8: 00000180000FF2B0
R9: 0000000000000001
R10: 00000180000FF2C8
R11: 0000000000000202
RBX: 00000180000FF6D8
RBP: 0000000000000000
R12: 0000000000CD513B
R13: 000000000000001C
R14: 00000180000FF670
R15: 0000000000FAE7D0
FS: 0000000000000033
TRACE: FFFFFE80004302D8
FFFFFE80004302D8: FFFFFF000013DF55
FFFFFF000013DE70+00E5
kernel::arch::x86_64::interrupt::exception::invalid_opcode::inner
FFFFFE8000430348: FFFFFF000013B69B
FFFFFF000013B670+002B
kernel::arch::x86_64::interrupt::exception::invalid_opcode
0000000000000000: GUARD PAGE
SIGNAL 4, CPU 0, PID ContextId(53)
NAME file:/bin/netsurf-fb
```
The browser window opens but it is not possible to close it or to kill the corresponding process
## Environment info
- Redox OS Release:
built version myself
- Operating system:
Fedora 31
- `uname -a`:
Linux localhost.localdomain 5.5.8-200.fc31.x86_64 #1 SMP Thu Mar 5 21:28:03 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
- `rustc -V`:
rustc 1.41.0-nightly (412f43ac5 2019-11-24)
- `git rev-parse HEAD`:
914f54f3ed4bc85d1e556b6fcd56ecc10a0d06a9
## Steps to reproduce
1. execute redox via `make qemu`
2. login with root:password
3. start the browser by clicking on the icon in the system tray
## Behavior
make qemu
```
SDL_VIDEO_X11_DGAMOUSE=0 qemu-system-x86_64 -d cpu_reset -d guest_errors -smp 4 -m 2048 -serial mon:stdio -machine q35 -device ich9-intel-hda -device hda-duplex -netdev user,id=net0 -device e1000,netdev=net0 -object filter-dump,id=f1,netdev=net0,file=build/network.pcap -device nec-usb-xhci,id=xhci -device usb-tablet,bus=xhci.0 -enable-kvm -cpu host \
-drive file=build/harddrive.bin,format=raw \
-drive file=build/extra.bin,format=raw
Kernel: 100000:AB2E78
Stack: FFFFFF0000080000:FFFFFF000009F000
Env: FFFFFF000009EFB0:FFFFFF000009F000
MemoryArea { base_addr: 0, length: 654336, _type: 1, acpi: 0 }
MemoryArea { base_addr: 654336, length: 1024, _type: 2, acpi: 0 }
MemoryArea { base_addr: 983040, length: 65536, _type: 2, acpi: 0 }
MemoryArea { base_addr: 1048576, length: 2146291712, _type: 1, acpi: 0 }
MemoryArea { base_addr: 2147340288, length: 143360, _type: 2, acpi: 0 }
MemoryArea { base_addr: 2952790016, length: 268435456, _type: 2, acpi: 0 }
MemoryArea { base_addr: 4275159040, length: 16384, _type: 2, acpi: 0 }
MemoryArea { base_addr: 4278173696, length: 16384, _type: 2, acpi: 0 }
MemoryArea { base_addr: 4294705152, length: 262144, _type: 2, acpi: 0 }
Using PIT
BSP: Ok(ContextId(1)) 1
Env: Ok("REDOXFS_BLOCK=0000000000000005\nREDOXFS_UUID=dcc05fe2-adb2-46c8-adcf-7fcaf7419d0b")
dlsym(0x0, pipe2)
dlsym: tcb not found
```https://gitlab.redox-os.org/redox-os/redox/-/issues/575clock_gettime doesn't always return an updated time2018-06-15T11:40:03ZJeremy Sollerclock_gettime doesn't always return an updated time*Created by: glegris*
**Reproduction**:
Inside a process, successive calls of clock_gettime gives the same time value, except if sleep is called between the calls. The code below allows to reproduce the 2 behaviors.
1) Compile the tes...*Created by: glegris*
**Reproduction**:
Inside a process, successive calls of clock_gettime gives the same time value, except if sleep is called between the calls. The code below allows to reproduce the 2 behaviors.
1) Compile the test code:
i386-elf-redox-gcc -o time_test time_test.c
2) Test 1 currently fails (simple loop between two calls of clock_gettime)
time_test
3) Test 2 (sleep between two clock_gettime calls)
time_test sleep
**Expected behavior**:
timespec should be updated between successive calls to clock_gettime
I provide the source code below as attachment doesn't work for me (!)
---
# include <stdlib.h>
# include <stdio.h>
# include <dirent.h>
# include <sys/time.h>
# include <time.h>
# include <unistd.h>
int main(int argc, char *\* argv){
printf("Test %d\n", argc);
int i;
for(i = 0; i < argc; i++){
printf("%d: %s\n", i, argv[i]);
}
```
struct timespec tp;
clock_gettime(CLOCK_REALTIME, &tp);
int start_time = (int)tp.tv_sec;
printf("clock_gettime start %d %d\n", (int)tp.tv_sec, (int)tp.tv_nsec);
int a = 64;
if (argc > 1) {
sleep(2);
} else {
for(i = 1; i < 100000000; i++){
a += a / i;
}
}
clock_gettime(CLOCK_REALTIME, &tp);
printf("clock_gettime end %d %d\n", (int)tp.tv_sec, (int)tp.tv_nsec);
if ((int)tp.tv_sec - start_time < 2) {
printf("Oops ! time was not updated !\n");
} else {
printf("OK\n");
}
printf("%i\n", a);
```
}
https://gitlab.redox-os.org/redox-os/redox/-/issues/598Redox will not boot(Virtualbox, Mac OSX)2018-06-15T11:40:03ZJeremy SollerRedox will not boot(Virtualbox, Mac OSX)*Created by: ghost*
I just tried to boot the virtual box .vdi file from the website, when I start the machine this is all I get:
![screen shot 2016-03-29 at 1 48 21 pm](https://cloud.githubusercontent.com/assets/13714106/14123420/42b02a...*Created by: ghost*
I just tried to boot the virtual box .vdi file from the website, when I start the machine this is all I get:
![screen shot 2016-03-29 at 1 48 21 pm](https://cloud.githubusercontent.com/assets/13714106/14123420/42b02abe-f5b5-11e5-94dc-1a87a72242a4.png) .
https://gitlab.redox-os.org/redox-os/redox/-/issues/450page fault when closing terminal window2018-06-15T11:40:03ZJeremy Sollerpage fault when closing terminal window*Created by: dufresnep*
got a page fault while playing around:
paul@arcturus:~/redox/redox$ make qemu kvm=no
find filesystem -not -path '_/._' -type f -o -type l | cut -d '/' -f2- | sort | awk '{printf("file %d,\"%s\"\n", NR, $0)}' > b...*Created by: dufresnep*
got a page fault while playing around:
paul@arcturus:~/redox/redox$ make qemu kvm=no
find filesystem -not -path '_/._' -type f -o -type l | cut -d '/' -f2- | sort | awk '{printf("file %d,\"%s\"\n", NR, $0)}' > build/i386/filesystem.gen
nasm -f bin -o build/i386/harddrive.bin -D ARCH_i386 -ibuild/i386/ -ikernel/ -ifilesystem/ kernel/harddrive.asm
qemu-system-i386 -serial mon:stdio -m 1024 -d guest_errors -vga std -usb -device usb-tablet -drive file=build/i386/harddrive.bin,format=raw,index=0,media=disk -net nic,model=rtl8139 -net user -net dump,file=build/i386/network.pcap
Redox 32 bits
ACPI Table: FACP
ACPI Table: SSDT
ACPI Table: APIC
MADT: Unknown entry type: 4, length 6
ACPI Table: HPET
Unknown Table
- PCI 0, 0, 0: ID 12378086 CL 6000002
- PCI 0, 1, 0: ID 70008086 CL 6010000
- PCI 0, 1, 1: ID 70108086 CL 1018000 BAR4: C121 16
IDE on C120
Primary Master: Status: 58 Serial: QM00001 Firmware: 2.5+ Model: QEMUHARDDISK Size: 39 MB
Primary Slave: Status: 0
Secondary Master: Status: 41 Error: 2
Secondary Slave: Status: 0
Redox Filesystem
- PCI 0, 1, 2: ID 70208086 CL C030001 BAR4: C101 32
UHCI on: C100, IRQ: B
CMD 00 to 00 to 00 STS 20 INTR 00 FRNUM 68 to 00 FLBASEADD 00 to B45000 CMD 00 to 01
PORTSC1 83 to 0283 to 83
Device Found 83 to 87
DeviceDescriptor {
length: 18,
descriptor_type: 1,
usb_version: 512,
class: 0,
sub_class: 0,
protocol: 0,
max_packet_size: 8,
vendor: 1575,
product: 1,
release: 0,
manufacturer_string: 1,
product_string: 3,
serial_string: 5,
configurations: 1
}
Manufacturer: QEMU
Product: QEMU USB Tablet
Serial: 42
ConfigDescriptor {
length: 9,
descriptor_type: 2,
total_length: 34,
interfaces: 1,
number: 1,
string: 7,
attributes: 160,
max_power: 50
}
Configuration: HID Tablet
InterfaceDescriptor {
length: 9,
descriptor_type: 4,
number: 0,
alternate: 0,
endpoints: 1,
class: 3,
sub_class: 0,
protocol: 2,
string: 0
}
HIDDescriptor {
length: 9,
descriptor_type: 33,
hid_version: 1,
country_code: 0,
descriptors: 1,
sub_descriptor_type: 34,
sub_descriptor_length: 74
}
EndpointDescriptor {
length: 7,
descriptor_type: 5,
address: 129,
attributes: 3,
max_packet_size: 8,
interval: 10
}
PORTSC2 80 to 0280 to 80
- PCI 0, 1, 3: ID 71138086 CL 6800003
- PCI 0, 2, 0: ID 11111234 CL 3000002 BAR0: FD000008 16777216 BAR2: FEBD0000 4096
- PCI 0, 3, 0: ID 813910EC CL 2000020 BAR0: C001 256 BAR1: FEBD1000 256
RTL8139 on: C000 port mapped IRQ: 0B MAC: 52.54.0.12.34.56 IMR: 05 CMD: 0D RCR: 9E TCR: 77800000
Starting HID driver
- Starting Orbital
Console: Press F1
Desktop: Press F2
redox login: PID 20: file:/apps/terminal/main.bin
INT E: Page fault
CS: 0000001B IP: 0804A8C6 FLG: 00000216
SS: 00000000 SP: 700FEDF0 BP: 700FFF20
AX: FFFFFFFF BX: 080576A8 CX: 00000000 DX: 00000000
DI: 083EA000 SI: 083EA000
CR0: 80000013 CR2: 083EB004 CR3: 00200000 CR4: 00000600
-480: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-448: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-416: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-384: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-352: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-320: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-288: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-256: 00000000 0804B260 700FEEB0 00000000 00000000 00000000 00000000 00000000
-224: 00000000 00000000 00000003 FFFFFFFF FFFFFFFF 00000240 00000190 00000008
-192: 700FEE70 00000000 1DFFFFFF FA000002 3B000000 1D1D1D1D 1D1D1D1D 1D1D1D1D
-160: 1D1D1D1D 1D1D1D1D 1D1D1D1D 1D1D1D1D 1D1D1D1D 1D1D1D1D 1D1D1D1D 00000020
-128: 00000000 0804B080 700FFF08 00000004 00000003 00000006 00000005 00000000
-96: 083EB000 083EB000 00000004 083EA000 1D1D1DD4 00000000 00000000 00000000
-64: 00000000 00000000 0804E5D8 00000001 00000000 00000000 00000000 00000000
-32: 0000000C 00000000 00000000 08049DD0 080576A8 00000000 00000000 00000000
0: 00000000 0804A8C1 080576A8 083EA000 083EB000 00000000 08049FCE 700FFF20
32: 080576A8 083EA010 00000000 083E9018 083E9018 00000000 00000000 0804A18E
64: 080576A8 083EA000 083EA010 00000000 00000000 08063000 08063000 00000001
96: 083EA000 00000048 00000190 00000000 00000019 00000190 FFFFFFFF 00000000
128: 00000000 0804A849 080576A8 083EA000 08063000 08065000 0804B9AC 080576A8
160: 083EA000 700FEDA8 00000010 FFFFFFFF 0000001E 0804B23A 080576A8 0000001E
192: FFFFFFFF 0804B12A 0804FF0F 700FEDA8 00000000 700FED48 700FEDC8 0804DB92
224: 080576A8 00000000 0804A3C3 700FEDA0 080576A8 0804FF0F 700FEDB0 0804A247
256: 00000008 0804B4C5 080576A8 00000000 0804E5D8 00000000 00000000 700FED3C
288: 080576A8 00000001 700FED48 00000000 00000000 0804A2E0 00000000 0804E5D8
320: 700FEDE8 0804D36D 080576A8 00000000 0804AAB4 700FED04 080576A8 0804FF0F
352: 00000000 00000000 00000000 00000011 0804E5A0 00000008 00000000 00000000
384: 00000000 00000011 0804E5A0 00000011 0804FD90 0804E371 080576A8 00000011
416: 0804E940 700FECA0 080576A8 0804E5D8 080576A8 00000001 700FED61 00000000
448: 00000000 0804A247 080576A8 700FEDB8 00000000 00000000 00000000 0804C1C0
480: 080576A8 700FEDB8 00000000 00000000 00000000 00000000 00000000 700FFEF0
ERR: 00000007
https://gitlab.redox-os.org/redox-os/redox/-/issues/536Allocations at 0x8408000 clear loaded applications2018-06-15T11:40:03ZJeremy SollerAllocations at 0x8408000 clear loaded applicationsThe kernel clears memory on allocation for security reasons. It does not properly page the memory when it clears, so allocations that reach 0x8408000 in physical memory will clear sections in virtual memory. This could be fixed by paging...The kernel clears memory on allocation for security reasons. It does not properly page the memory when it clears, so allocations that reach 0x8408000 in physical memory will clear sections in virtual memory. This could be fixed by paging in the memory correctly before clearing, or clearing in the sys_alloc and sys_realloc functions after the memory has been mapped
https://gitlab.redox-os.org/redox-os/redox/-/issues/599Page fault triggered by sdl-test2018-06-15T11:40:03ZJeremy SollerPage fault triggered by sdl-test*Created by: FreeFull*
**Reproduction**:
Run either `make qemu` or `make virtualbox`
Select the 800x600 screen resolution
Start orbital, open a terminal and run `sdl-test`
Press esc repeatedly until the system freezes
**Build informati...*Created by: FreeFull*
**Reproduction**:
Run either `make qemu` or `make virtualbox`
Select the 800x600 screen resolution
Start orbital, open a terminal and run `sdl-test`
Press esc repeatedly until the system freezes
**Build information**:
`rustc -V`
rustc 1.9.0-nightly (a1e29daf1 2016-03-25)
`git rev-parse HEAD`
b76ecf3d0fcd225846d481b7efeab3f0b1c65143
`qemu-system-i386 --version`
QEMU emulator version 2.5.0, Copyright (c) 2003-2008 Fabrice Bellard
`uname -a`
Linux freefull-asus 4.4.5-1-ARCH # 1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux
Page fault debug output:
```
INT E: Page fault
CS: 00000008 IP: 00000000 FLG: 00010002
SS: 00000000 SP: 041B5000 BP: 05FACD28
AX: 05FACCEC BX: 838F8000 CX: 83416000 DX: 03D48B5C
DI: 80BDB000 SI: 80BDB000
CR0: 80010033 CR2: 00000000 CR3: 00200000 CR4: 00000600
FSW: 00000000 FCW: 0000037F
-480: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-448: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-416: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-384: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-352: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-320: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-288: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-256: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-224: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-192: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-160: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-128: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-96: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-64: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
-32: 00000000 00000000 00000000 00000000 00000000 00074FE0 0000000F 0000000F
0: 841B3000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
32: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
64: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
96: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
128: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
160: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
192: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
224: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
256: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
288: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
320: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
352: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
384: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
416: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
448: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
480: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ERR: 00000000
```
**Additional information**:
The sdl-test window always seems to be displaying white when the page fault happens.
https://gitlab.redox-os.org/redox-os/redox/-/issues/623Use after free in `SupervisorResource`2018-06-15T11:40:03ZJeremy SollerUse after free in `SupervisorResource`*Created by: ticki*
**Reproduction**: Overwriting or dropping a supervised context (e.g., sys_exit) will not destroy the supervisor as well, making the supervisor hold a dangling ponter. This potentially allows a context to supervise a ...*Created by: ticki*
**Reproduction**: Overwriting or dropping a supervised context (e.g., sys_exit) will not destroy the supervisor as well, making the supervisor hold a dangling ponter. This potentially allows a context to supervise a context, which isn't even a child.
**Expected behavior**: Drop or invalidate the supervisor resource when the context drops.
Although, this is fairly harmless currently, due to how contexts are stored, changes in the future can cause security vulnerabilities.
See `kernel/fs/supervisor_resource.rs`.
https://gitlab.redox-os.org/redox-os/redox/-/issues/916Exit command doesn't work2018-06-15T11:40:01ZJeremy SollerExit command doesn't work*Created by: mnbvcxzlkjhgfdsapoiu*
*Created by: mnbvcxzlkjhgfdsapoiu*
Jeremy SollerJeremy Sollerhttps://gitlab.redox-os.org/redox-os/redox/-/issues/877rustc no longer supports $(ARCH)-unknown-none as known target2018-06-15T11:40:00ZJeremy Sollerrustc no longer supports $(ARCH)-unknown-none as known target*Created by: Dragonrun1*
Among other issues I've been noticing when manually running some of the build commands to figure needed changes to make stuff build under MS Windows I've ran into this one which I sure isn't just a Windows only ...*Created by: Dragonrun1*
Among other issues I've been noticing when manually running some of the build commands to figure needed changes to make stuff build under MS Windows I've ran into this one which I sure isn't just a Windows only issue. For example when trying to run:
`bash
CARGO_INCREMENTAL=1 cargo rustc --manifest-path rust/src/libcollections/Carg
o.toml --target x86_64-unknown-none --release --verbose -- -C soft-float -o bui
ld/kernel/libcollections.rlib
`
I get
`bash
error: failed to run `rustc` to learn about target-specific information
Caused by:
process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --target x86_64-unknown-none` (exit code: 101)
--- stderr
error: Error loading target specification: Could not find specification for target "x86_64-unknown-none"
|
= help: Use `--print target-list` for a list of built-in targets
`
and when I run:
`bash
$ rustc --print target-list
`
It no longer list any `-unknown-none` targets. I'm not sure when rust made the change but the KTARGET of the mk/config.mk file needs to be updated. My suggestion would be something like `$(ARCH)-unknown-linux-gnu`. I didn't check but I'm pretty sure those are what the old `-none` targets have been renamed too and at least in some limited testing seem to work. I noticed this as well in the build history which shows the error I get without the `--verbose` option added.
https://travis-ci.org/redox-os/redox/builds/211931652Jeremy SollerJeremy Soller