Best reference for understanding core file and debugging for different architectures Post: 302950965

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Debugging core file from another server

Hi all, One fine day one of the services in our prod server started core dumping and then the core file was ftp'd to our test server , to debug we used gdb with the executable which we had but we could not get the function names ( maybe due to missing symbols ) How do i solve this ...

2. IP Networking

Best reference for understanding low level info on nic cards drivers and functionality

Hi, What is the best reference that gives in detail on nic cards configuration , assigning multiple ip addresses to a single interface, netlink library etc and all basic stuff at this level..? Thanks

3. Shell Programming and Scripting

Perl de-reference code reference variable

Guys, May i know how can we de reference the code reference variable.? my $a = sub{$a=shift;$b=shift;print "SUM:",($a+$b),"\n";}; print $a->(4,5); How can we print the whole function ? Please suggest me regarding this. Thanks for your time :) Cheers, Ranga :)

4. Shell Programming and Scripting

Problem in understanding debugging

Hi i was going through the script debugging technique. below example was given in the book. 1 #!/bin/sh 2 3 Failed() { 4 if ; then 5 echo "Failed. Exiting." ; exit 1 ; 6 fi 7 echo "Done." 8 } 9 10 echo "Deleting old backups,...

5. Red Hat

Gdb error while debugging core file

Hi, I am trying to analyze one core file on my RHEL 6.5, but I am getting below error related to the core file. So I am not getting any stack trace about the crash. # gdb MyDebugBin /var/core/MyDebugBin.27005 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) Copyright (C) 2010 Free...

6. Shell Programming and Scripting

Keeping record of file 2 based on a reference file 1 in awk

I have 2 input files (tab separated): file1: make_A 1990 foo bar make_B 2010 this that make_C 2004 these those file2: make_X 1970 1995 ref_1:43 ref_2:65 make_A 1970 1995 ref_1:4 ref_2:21 ref_3:18 make_A 1980 2002 ref_1:7 ref_2:7 ref_3:0 ...

7. UNIX for Dummies Questions & Answers

awk to replace values in one file using a second reference file

Hi, I'd be grateful for your help with the following: I have a file with a single column (file1). Let's say the values are: a b c 5 d I have a second, reference file (ref_file), which is colon-delimited, and is effectively a key. Let's say the values in it are: a:1 b:2 c:3 d:4...

LEARN ABOUT LINUX

platform

platform(n)						       Tcl Bundled Packages						       platform(n)

__________________________________________________________________________________________________________________________________________________

NAME

       platform - System identification support code and utilities

SYNOPSIS

       package require platform ?1.0.4?

       platform::generic
       platform::identify
       platform::patterns identifier
_________________________________________________________________

DESCRIPTION

       The platform package provides several utility commands useful for the identification of the architecture of a machine running Tcl.

       Whilst Tcl provides the tcl_platform array for identifying the current architecture (in particular, the platform and machine elements) this
       is not always sufficient. This is because (on Unix machines) tcl_platform reflects the values returned by the uname command and	these  are
       not standardized across platforms and architectures. In addition, on at least one platform (AIX) the tcl_platform(machine) contains the CPU
       serial number.

       Consequently, individual applications need to manipulate the values in tcl_platform (along with the output of system specific utilities)  -
       which is both inconvenient for developers, and introduces the potential for inconsistencies in identifying architectures and in naming con-
       ventions.

       The platform package prevents such fragmentation - i.e., it establishes a standard naming convention  for  architectures  running  Tcl  and
       makes it more convenient for developers to identify the current architecture a Tcl program is running on.

COMMANDS

       platform::identify
	      This  command returns an identifier describing the platform the Tcl core is running on. The returned identifier has the general for-
	      mat OS-CPU. The OS part of the identifier may contain details like kernel version, libc version, etc., and this information may con-
	      tain dashes as well.  The CPU part will not contain dashes, making the preceding dash the last dash in the result.

       platform::generic
	      This  command  returns a simplified identifier describing the platform the Tcl core is running on. In contrast to platform::identify
	      it leaves out details like kernel version, libc version, etc. The returned identifier has the general format OS-CPU.

       platform::patterns  identifier
	      This command takes an identifier as returned by platform::identify and returns a list of identifiers describing compatible architec-
	      tures.

KEYWORDS

       operating system, cpu architecture, platform, architecture

platform							       1.0.4							       platform(n)