VirtualBox

Ticket #1530 (closed defect: duplicate)

Opened 6 years ago

Last modified 6 years ago

FreeBSD 7 sigreturn

Reported by: jbuhrt Owned by:
Priority: major Component: VMM
Version: VirtualBox 2.0.2 Keywords: sigreturn eflags freebsd
Cc: Guest type: BSD
Host type: other

Description

I am running Virtual Box 1.6.0, now maintained by Sun Microsystems. I am running

HOST: Windows x86 Vista Home Premium: Service Pack 1 GUEST: FreeBSD7-RELEASE

I have ran into the same issues. I just did a fresh install and ran into this problem, just as soon as I started to install nmap from ports: /usr/ports/security/nmap

As I was installing nmap a few programs were needed such as: gmake and gettext. As soon as gettext started to extract after being downloaded I ran into the problem: sigreturn: eflags = 0x80282

Here is some output:

cd /usr/ports/security/nmap make install && make clean

=> Attempting to fetch from  http://ftp.gnu.org/gnu/gettext/. gettext-0.16.1.tar.gz 100% of 8339 kB 77 kBps 00m00s ===> Extracting for gettext-0.16.1_3 => MD5 Checksum OK for gettext-0.16.1.tar.gz. => SHA256 Checksum OK for gettext-0.16.1.tar.gz. sigreturn: eflags = 0x80282

I see this problem resides in FreeBSD6.2-RELEASE, and is also present in FreeBSD7-RELEASE. Any ideas? Thanks.

Change History

comment:1 Changed 6 years ago by frank

  • Component changed from other to VMM
  • Guest type changed from other to BSD

comment:2 Changed 6 years ago by jsingleton

This is verified to be *NOT* fixed in v1.6.2 either. Even doing something as simple as updating ports kill the guest OS. This is being ignored for some reason.

<snip> Building new INDEX files... done. sigreturn: eflags - 0x80203

WHEN IS THIS GOING TO BE FIXED!!!

comment:3 follow-up: ↓ 4 Changed 6 years ago by sandervl73

Asking for a fix like this doesn't encourage us, that's for sure. We are aware of the issue.

comment:4 in reply to: ↑ 3 Changed 6 years ago by jsingleton

Replying to sandervl73:

Asking for a fix like this doesn't encourage us, that's for sure. We are aware of the issue.

It's been an issue since v1.4.0 ... how many more releases before it is fixed.

Maybe a response to the original issue back in 2007 would prompt better ethics on my part. It appears this issue has been ignored, yet VirtualBox has had several new releases since. Yeah I know it's free, but ignoring huge bugs like this simply is no way to maintain a happy community.

comment:5 Changed 6 years ago by frank

  • Status changed from new to closed
  • Version changed from VirtualBox 1.6.0 to VirtualBox 2.0.2
  • Resolution set to duplicate

Duplicate of #2431.

comment:6 follow-up: ↓ 7 Changed 6 years ago by dnelson

Duplicate of #2341 instead, I think?

comment:7 in reply to: ↑ 6 ; follow-up: ↓ 8 Changed 6 years ago by jsingleton

Replying to dnelson:

Duplicate of #2341 instead, I think?

How can #1530 be a duplicate of #2431. Doesn't 1530 come before 2341? My ticket was open in July, 2341 was open last week.

It should read, 2341 is a duplicate of 1530...

comment:8 in reply to: ↑ 7 Changed 6 years ago by dnelson

Replying to jsingleton:

I was just correcting the ticket number, not arguing which is supposed to a duplicate of the other. Actually, both are probably dupes of #458 :) No need to open a new bug every time a new version of VBox is released.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use