blob: 1e5d669b97a499952c4948b3243dbb983d373d06 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to classify this bug report as either 'user' or 'system'. The issue is that when using qemu-user on a Debian/m68k system, the shell variable $0 reports an absolute path instead of just the command name.
So, looking at the details: When running 'sh -c 'echo $0'', under normal conditions it outputs 'sh', but with qemu-user, it shows '/bin/sh'. This suggests that the emulation is affecting how the shell perceives its own execution environment.
Qemu has two main modes: user-mode and system-mode. User-mode emulates just the CPU instructions without a full OS, while system-mode emulates an entire machine including hardware devices.
In this case, since the problem occurs when running under qemu-user (as indicated in the report), it's about how the shell is executing within that environment. The issue relates to how arguments and variables are passed or interpreted by the user-space programs. This points more towards a user-mode emulation bug because it's affecting how the shell script runs, not the underlying system hardware or device drivers.
Therefore, this should be classified as 'user'.
</think>
user
|