Application not working in multi core platform Post: 302911828

3 More Discussions You Might Find Interesting

1. Programming

Multi-platform includes?

I know that <cstudio> can also be <stdio> and can be written different ways on Linux then with windows. I've see some code doing a IFDEF __APPLE__ (I'm guessing, if compiled on a mac do whats between this) Is there one for Linux/Window?

2. UNIX for Advanced & Expert Users

Multi-platform Centralized Patch Management

We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our...

3. Shell Programming and Scripting

Multi platform script perl or awk

Hi gurus, I am trying to match records in following format: (-,username,domain1.co.uk)\ (-,username,domain2.co.uk) either awk or perl must be used. I am using cygwin. I wrote following code which works and matches both above entries: awk 'BEGIN {musr="(-,username,+.co.uk)"} {if...

LEARN ABOUT HPUX

gcore

gcore(1)						      General Commands Manual							  gcore(1)

NAME

       gcore - get core images of running processes

SYNOPSIS

       filename] process-id...

DESCRIPTION

       The command creates a core image of each specified process.  By default, the name of the core image file for process-id will be The process
       information in the core file can be obtained by using debuggers.

       When the command creates a core image of each specified process, the process is temporarily stopped.  Further, when the	creation  of  core
       image is complete, the process continues to execute.

   Options
       Creates the core file with name of the file as
		      If multiple process-id values are specified, filename will be common for all the core image files.  See the section.

   Operands
       process-id     The process ID for which a core image file will be created.

RETURN VALUE

       Upon completion, exits with one of the following values:

	      A core file was successfully created.

	      An error condition was encountered.
		     In such a case, the creation of a core file is not guaranteed.  The error conditions could be because of

		     o	A nonexistent or incorrect process ID was specified.

		     o	An invalid option was specified.

		     o	The current working directory of the process or directory from which was invoked had no write permissions.

		     o	The current working directory of the process was not accessible.

		     o	The file system is full.

EXAMPLES

   Example 1
       Dump the core image of process 1030 in the file "core.1030".

   Example 2
       Dump the core image of the process 1030 in the file "test.1030".

   Example 3
       Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files "core.1030", "core.1031", "core.1032", "core.1033".

   Example 4
       Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files

FILES

       Core image file for process-id.	(Both where is invoked and the current working directory of the process.)

AUTHOR

       was developed by Chris Bertin (HP).

SEE ALSO

       adb(1), gdb(1), kill(1), ttrace(2), a.out(4), core(4).

																	  gcore(1)