Sponsored Content
Operating Systems Linux ARM Cortex A9 Core-'1' Execution Sequence Post 302557754 by tkarthi85 on Thursday 22nd of September 2011 04:27:11 AM
Old 09-22-2011
Hi,

omap_secondary_startup is the start address for CORE-1, after SEV is triggered from CORE-0. This address is programmed in AUXCOREBOOT1 register using omap_auxcoreboot_addr() function.

Sorry for your 2nd and 3rd question.

Regards,
karthi
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

difference between Dual-core & Core-to-duo

Can anybody tell What is the exact difference between a Dual-core processor and a Core-to-duo processor ?Advance thanks to all my friends. (1 Reply)
Discussion started by: Ajith kumar.G
1 Replies

2. Programming

execution failure and core dump generation

Hi, I am running a c++ program in unix sun OS 5.9. There are two functions in a file which are being used by a third function in the same file. the two functions being used are of the same type. one function is returning a success and the control is redeemed by the calling function. for teh second... (2 Replies)
Discussion started by: suresh_kb211
2 Replies

3. Programming

execution failure and core dump generation

Hi, I am running a c++ program in unix sun OS 5.9. There are two functions in a file which are being used by a third function in the same file. the two functions being used are of the same type. one function is returning a success and the control is redeemed by the calling function. for teh second... (5 Replies)
Discussion started by: suresh_kb211
5 Replies

4. Programming

mysterious execution failure and core dump generation

Posting again, as previous query had a typo. ======================================================= Hi, I am running a c++ program in unix AIX machine. There are two functions in a file which are being used by a third function in the same file. the two functions being used are of the same type.... (1 Reply)
Discussion started by: suresh_kb211
1 Replies

5. Shell Programming and Scripting

Expect Issue Serial Forground Execution vs Concurrent Background Execution

I have an expect script that interrogates several hundred unix servers for both access and directories therein using "ssh user@host ls -l /path". The combination of host/path are unique but the host may be interrogated multiple times if there are multiple paths to test. The expect script is run... (2 Replies)
Discussion started by: twk
2 Replies

6. Programming

gcc for arm process

hi, correct me if am wrong, as per gcc doc gcc is able to compile code for different target systems such as ARM, ARC etc. I tried for compiling ARM but failed to do so. getting below error: gcc -mcpu=arm920t -c avg.c -o agv_arm `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.... (6 Replies)
Discussion started by: zing_foru
6 Replies

7. Shell Programming and Scripting

find common entries and match the number with long sequence and cut that sequence in output

Hi all, I have a file like this ID 3BP5L_HUMAN Reviewed; 393 AA. AC Q7L8J4; Q96FI5; Q9BQH8; Q9C0E3; DT 05-FEB-2008, integrated into UniProtKB/Swiss-Prot. DT 05-JUL-2004, sequence version 1. DT 05-SEP-2012, entry version 71. FT COILED 59 140 ... (1 Reply)
Discussion started by: manigrover
1 Replies

8. High Performance Computing

IBM Hardware: Test speed of an execution core reliably.

Hey Folks, Doing simple floating point or integer arithmetic is limited since if another execution core is not busy, the system will (presumably?) assign CPU resources to where they are needed so I could be getting the performance of 2 or more cores theoretically? Any good reliable way to... (2 Replies)
Discussion started by: Devyn
2 Replies

9. Shell Programming and Scripting

Script execution in sequence manner

Hi guys, I am building a parent script which will call three scripts internally and i would like to run them in sequence manner, i.e. once previous script is successful then only i need to proceed with next else need to fail. I am running in bash mode and flavour is sun main_script.sh sh... (8 Replies)
Discussion started by: Master_Mind
8 Replies
autodie::exception(3pm) 				 Perl Programmers Reference Guide				   autodie::exception(3pm)

NAME
autodie::exception - Exceptions from autodying functions. SYNOPSIS
eval { use autodie; open(my $fh, '<', 'some_file.txt'); ... }; if (my $E = $@) { say "Ooops! ",$E->caller," had problems: $@"; } DESCRIPTION
When an autodie enabled function fails, it generates an "autodie::exception" object. This can be interrogated to determine further information about the error that occurred. This document is broken into two sections; those methods that are most useful to the end-developer, and those methods for anyone wishing to subclass or get very familiar with "autodie::exception". Common Methods These methods are intended to be used in the everyday dealing of exceptions. The following assume that the error has been copied into a separate scalar: if ($E = $@) { ... } This is not required, but is recommended in case any code is called which may reset or alter $@. args my $array_ref = $E->args; Provides a reference to the arguments passed to the subroutine that died. function my $sub = $E->function; The subroutine (including package) that threw the exception. file my $file = $E->file; The file in which the error occurred (eg, "myscript.pl" or "MyTest.pm"). package my $package = $E->package; The package from which the exceptional subroutine was called. caller my $caller = $E->caller; The subroutine that called the exceptional code. line my $line = $E->line; The line in "$E->file" where the exceptional code was called. context my $context = $E->context; The context in which the subroutine was called. This can be 'list', 'scalar', or undefined (unknown). It will never be 'void', as "autodie" always captures the return value in one way or another. return my $return_value = $E->return; The value(s) returned by the failed subroutine. When the subroutine was called in a list context, this will always be a reference to an array containing the results. When the subroutine was called in a scalar context, this will be the actual scalar returned. errno my $errno = $E->errno; The value of $! at the time when the exception occurred. NOTE: This method will leave the main "autodie::exception" class and become part of a role in the future. You should only call "errno" for exceptions where $! would reasonably have been set on failure. eval_error my $old_eval_error = $E->eval_error; The contents of $@ immediately after autodie triggered an exception. This may be useful when dealing with modules such as Text::Balanced that set (but do not throw) $@ on error. matches if ( $e->matches('open') ) { ... } if ( $e ~~ 'open' ) { ... } "matches" is used to determine whether a given exception matches a particular role. On Perl 5.10, using smart-match ("~~") with an "autodie::exception" object will use "matches" underneath. An exception is considered to match a string if: o For a string not starting with a colon, the string exactly matches the package and subroutine that threw the exception. For example, "MyModule::log". If the string does not contain a package name, "CORE::" is assumed. o For a string that does start with a colon, if the subroutine throwing the exception does that behaviour. For example, the "CORE::open" subroutine does ":file", ":io" and ":all". See "CATEGORIES" in autodie for futher information. Advanced methods The following methods, while usable from anywhere, are primarily intended for developers wishing to subclass "autodie::exception", write code that registers custom error messages, or otherwise work closely with the "autodie::exception" model. register autodie::exception->register( 'CORE::open' => &mysub ); The "register" method allows for the registration of a message handler for a given subroutine. The full subroutine name including the package should be used. Registered message handlers will receive the "autodie::exception" object as the first parameter. add_file_and_line say "Problem occurred",$@->add_file_and_line; Returns the string " at %s line %d", where %s is replaced with the filename, and %d is replaced with the line number. Primarily intended for use by format handlers. stringify say "The error was: ",$@->stringify; Formats the error as a human readable string. Usually there's no reason to call this directly, as it is used automatically if an "autodie::exception" object is ever used as a string. Child classes can override this method to change how they're stringified. format_default my $error_string = $E->format_default; This produces the default error string for the given exception, without using any registered message handlers. It is primarily intended to be called from a message handler when they have been passed an exception they don't want to format. Child classes can override this method to change how default messages are formatted. new my $error = autodie::exception->new( args => @_, function => "CORE::open", errno => $!, context => 'scalar', return => undef, ); Creates a new "autodie::exception" object. Normally called directly from an autodying function. The "function" argument is required, its the function we were trying to call that generated the exception. The "args" parameter is optional. The "errno" value is optional. In versions of "autodie::exception" 1.99 and earlier the code would try to automatically use the current value of $!, but this was unreliable and is no longer supported. Atrributes such as package, file, and caller are determined automatically, and cannot be specified. SEE ALSO
autodie, autodie::exception::system LICENSE
Copyright (C)2008 Paul Fenwick This is free software. You may modify and/or redistribute this code under the same terms as Perl 5.10 itself, or, at your option, any later version of Perl 5. AUTHOR
Paul Fenwick <pjf@perltraining.com.au> perl v5.18.2 2014-01-06 autodie::exception(3pm)
All times are GMT -4. The time now is 08:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy