Sponsored Content
Full Discussion: Exiting (caught signal 11)
Operating Systems Solaris Exiting (caught signal 11) Post 302897983 by Corona688 on Thursday 17th of April 2014 12:16:16 PM
Old 04-17-2014
Signal 11 means it's crashing. It really doesn't like your virtual machine for some reason. It might need different configuration or drivers.
 

8 More Discussions You Might Find Interesting

1. AIX

process caught signal 5

Hello, We are using AIX 5.2 ML 7. One of the process in its log file said the following and stopped running. Caught signal=5, exiting. What would cause the signal 5 to be generated on an AIX box. Please advise. Thx Jerardfjay (2 Replies)
Discussion started by: jerardfjay
2 Replies

2. Shell Programming and Scripting

My error is not being caught or handled

Hi, I my ksh script I have the following: ##--Checking the spool file for errors NumberOfErrors=`cat $CurrSpoolFile | grep " ORA-" | wc -l`my logfile shows this: PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. BEGIN... (1 Reply)
Discussion started by: ramangill
1 Replies

3. Solaris

Solaris 10 install issue - "Caught Signal 11"

Rebuilding a server (T2000) from a flash archive I created on another server. Using a Solaris 10/08 DVD to boot from the was going to point it tot he flash archive and pull it over NFS. I've done this many times with success until now. It initially boots off the DVD, you input the... (5 Replies)
Discussion started by: Probos
5 Replies

4. Solaris

Solaris 10 upgrade exiting ( caught signal 11)

Hi, I am pretty new to Solaris and am trying to upgrade from the OBP. I go through the process of booting from the cdrom, entering all necessary information and running the upgrade. The system completes analysis and then fail with the EXITING (caught signal 11) error I believe that... (5 Replies)
Discussion started by: Seanliam
5 Replies

5. Solaris

Exiting signal 6

Hello all, I have a problem when installing Solaris 10 on Enterprise 450. I booted from dvd, then the installation was started. The error appeared after determining the installation method, F2-Standard, F?-Flash...... The error was Exiting signal 6. Please, need help. Thank you (4 Replies)
Discussion started by: Hardono
4 Replies

6. Shell Programming and Scripting

Line numbers and exception to be caught in logs

Hi Folks, I have just basic queries is that suppose I have to monitor the logs then there is a command , suppose I have to monitor the abc.log which is updating dynamically within seconds so the command will be after going to that directory is .. tail -f abc.log Now please advise what about... (1 Reply)
Discussion started by: punpun66
1 Replies

7. Solaris

Solaris 10 "Exiting (caught signal 11)"

I get an error after the initializing screen. I am using a DVD/ROM to boot up the installation on a Dell Inspiron 1520. Segmentation fault - core dumped. I have tried to restart multiple times. Please help (1 Reply)
Discussion started by: Jimasaurus
1 Replies

8. Shell Programming and Scripting

Continue Processing after a signal is caught

Is it possible to continue after signal is caught and control goes to function specified in the trap statement? (3 Replies)
Discussion started by: Soham
3 Replies
set_gfx_mode(3alleg4)						  Allegro manual					     set_gfx_mode(3alleg4)

NAME
set_gfx_mode - Sets a graphic video mode. Allegro game programming library. SYNOPSIS
#include <allegro.h> int set_gfx_mode(int card, int w, int h, int v_w, int v_h); DESCRIPTION
Switches into graphics mode. The card parameter should usually be one of the Allegro magic drivers (read introduction of chapter "Graphics modes") or see the platform specific documentation for a list of the available drivers. The w and h parameters specify what screen resolu- tion you want. The color depth of the graphic mode has to be specified before calling this function with set_color_depth(). The v_w and v_h parameters specify the minimum virtual screen size, in case you need a large virtual screen for hardware scrolling or page flipping. You should set them to zero if you don't care about the virtual screen size. When you call set_gfx_mode(), the v_w and v_h parameters represent the minimum size of virtual screen that is acceptable for your program. The range of possible sizes is usually very restricted, and Allegro may end up creating a virtual screen much larger than the one you request. Allowed sizes are driver dependent and some drivers do not allow virtual screens that are larger than the visible screen at all: don't assume that whatever you pass will always work. In mode-X the virtual width can be any multiple of eight greater than or equal to the physical screen width, and the virtual height will be set accordingly (the VGA has 256k of vram, so the virtual height will be 256*1024/virtual_width). Currently, using a big virtual screen for page flipping is considered bad practice. There are platforms which don't support virtual screens bigger than the physical screen but can create different video pages to flip back and forth. This means that, if you want page flipping and aren't going to use hardware scrolling, you should call set_gfx_mode() with (0,0) as the virtual screen size and later create the different video pages with create_video_bitmap(). Otherwise your program will be limited to the platforms supporting hardware scrolling. After you select a graphics mode, the physical and virtual screen sizes can be checked with the macros SCREEN_W, SCREEN_H, VIRTUAL_W, and VIRTUAL_H. RETURN VALUE
Returns zero on success. On failure returns a negative number and stores a description of the problem in allegro_error. SEE ALSO
set_color_depth(3alleg4), request_refresh_rate(3alleg4), screen(3alleg4), gfx_capabilities(3alleg4), allegro_error(3alleg4), cre- ate_video_bitmap(3alleg4), get_desktop_resolution(3alleg4), SCREEN_W(3alleg4), SCREEN_H(3alleg4), VIRTUAL_W(3alleg4), VIRTUAL_H(3alleg4) Allegro version 4.4.2 set_gfx_mode(3alleg4)
All times are GMT -4. The time now is 09:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy