Sponsored Content
Full Discussion: Viewing files
Top Forums UNIX for Dummies Questions & Answers Viewing files Post 77335 by jim mcnamara on Thursday 7th of July 2005 09:59:09 AM
Old 07-07-2005
core is a dump of process memory. I do not know which debugger is on your system.
Basically, you debug the imagefile (.exe) that failed and examine the core file.

Most debuggers work something like this:
adb imagefilename core

where adb is the debugger, imagefilename is the .exe that bombed, and core is the name of the file.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem Viewing Text Files In NT/Samba

I have a problem viewing text files in NT(Samba) with files stored on a Unix Box. The unix box is actually my FTP server where various OS's FTP to it. The text file is ftp'd from IBM to the Unix Box and viewed in NT. The problem is that the return carriage does not register in the text file. I... (1 Reply)
Discussion started by: cwong
1 Replies

2. UNIX for Dummies Questions & Answers

Viewing files in a directory?

How do I view files in a directory? (1 Reply)
Discussion started by: Ania
1 Replies

3. UNIX for Advanced & Expert Users

viewing binary files in ASCII

Hi, How to view binary files in ASCII format.???????????????? Bye (2 Replies)
Discussion started by: manjunath
2 Replies

4. UNIX for Dummies Questions & Answers

Viewing Tar files

I have backed up a job ona ait tape from unix. i would like to retrieve the data from that tape from a windows pc. i am aware that there may be software available that will allow windows to recognise .tar files. does anyone know where i can source this software or is there any other options (1 Reply)
Discussion started by: mapping
1 Replies

5. UNIX for Dummies Questions & Answers

Viewing files of another unix server (in a folder)

I think that's what I'm trying to do. This is the problem: I log onto my comp, Comp1. Then, from the terminal, since my web server is on another comp, I type: xrlogin Comp2, so I log on to that computer. I then navigate to my directory by typing: cd /domain/myDir, so I am in my directory, on the... (3 Replies)
Discussion started by: Djaunl
3 Replies

6. UNIX for Dummies Questions & Answers

viewing/information of binary files

Hi all, Is there a way of viewing a binary file through a UNIX session? Or perhaps viewing information of a binary file through a session? thanks (2 Replies)
Discussion started by: ocelot
2 Replies

7. UNIX for Dummies Questions & Answers

Viewing Ebcidic files

I am having trouble viewing these files from my unix session. vi comes back with line too long. Also an m_dump with the relevant dml comes back with problems. How can I view this as a text file? Also is there an easy way to view specific records within. Eg I have a policy id (4 Replies)
Discussion started by: trek88
4 Replies

8. UNIX for Dummies Questions & Answers

viewing the *.msg files

Is there any way we can view the *.msg files in unix / linux ? Example cat aa.msg Or Do we need to do any decryption ? Kindly provide the solution? (0 Replies)
Discussion started by: kingganesh04
0 Replies

9. UNIX for Dummies Questions & Answers

Bourne shell viewing files in directory

Hi, I have a program that get a directory name from the user, then the program should go through one by one of the file, asking the user whether to move it to another folder. I tried to list the time of the file one by one. But it seems like it doesn't work. The code is as follow: check() {... (10 Replies)
Discussion started by: mInGzaiii
10 Replies

10. Shell Programming and Scripting

Help with viewing the Log files

I have a file name as logfiles_tar.tgz. How can I view the contents of the log files present in logfiles_tar.tgz ? Any help would be really appreciated. Thanks (3 Replies)
Discussion started by: bobby1015
3 Replies
CORE(3pm)						 Perl Programmers Reference Guide						 CORE(3pm)

NAME
CORE - Namespace for Perl's core routines SYNOPSIS
BEGIN { *CORE::GLOBAL::hex = sub { 1; }; } print hex("0x50")," "; # prints 1 print CORE::hex("0x50")," "; # prints 80 CORE::say "yes"; # prints yes BEGIN { *shove = &CORE::push; } shove @array, 1,2,3; # pushes on to @array DESCRIPTION
The "CORE" namespace gives access to the original built-in functions of Perl. The "CORE" package is built into Perl, and therefore you do not need to use or require a hypothetical "CORE" module prior to accessing routines in this namespace. A list of the built-in functions in Perl can be found in perlfunc. For all Perl keywords, a "CORE::" prefix will force the built-in function to be used, even if it has been overridden or would normally require the feature pragma. Despite appearances, this has nothing to do with the CORE package, but is part of Perl's syntax. For many Perl functions, the CORE package contains real subroutines. This feature is new in Perl 5.16. You can take references to these and make aliases. However, some can only be called as barewords; i.e., you cannot use ampersand syntax (&foo) or call them through references. See the "shove" example above. These subroutines exist for all keywords except the following: "__DATA__", "__END__", "and", "cmp", "default", "do", "dump", "else", "elsif", "eq", "eval", "for", "foreach", "format", "ge", "given", "goto", "grep", "gt", "if", "last", "le", "local", "lt", "m", "map", "my", "ne", "next", "no", "or", "our", "package", "print", "printf", "q", "qq", "qr", "qw", "qx", "redo", "require", "return", "s", "say", "sort", "state", "sub", "tr", "unless", "until", "use", "when", "while", "x", "xor", "y" Calling with ampersand syntax and through references does not work for the following functions, as they have special syntax that cannot always be translated into a simple list (e.g., "eof" vs "eof()"): "chdir", "chomp", "chop", "defined", "delete", "each", "eof", "exec", "exists", "keys", "lstat", "pop", "push", "shift", "splice", "split", "stat", "system", "truncate", "unlink", "unshift", "values" OVERRIDING CORE FUNCTIONS
To override a Perl built-in routine with your own version, you need to import it at compile-time. This can be conveniently achieved with the "subs" pragma. This will affect only the package in which you've imported the said subroutine: use subs 'chdir'; sub chdir { ... } chdir $somewhere; To override a built-in globally (that is, in all namespaces), you need to import your function into the "CORE::GLOBAL" pseudo-namespace at compile time: BEGIN { *CORE::GLOBAL::hex = sub { # ... your code here }; } The new routine will be called whenever a built-in function is called without a qualifying package: print hex("0x50")," "; # prints 1 In both cases, if you want access to the original, unaltered routine, use the "CORE::" prefix: print CORE::hex("0x50")," "; # prints 80 AUTHOR
This documentation provided by Tels <nospam-abuse@bloodgate.com> 2007. SEE ALSO
perlsub, perlfunc. perl v5.18.2 2013-11-04 CORE(3pm)
All times are GMT -4. The time now is 11:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy