Sponsored Content
Full Discussion: how to view a core dump file
Top Forums Programming how to view a core dump file Post 302157602 by ramen_noodle on Friday 11th of January 2008 12:15:24 PM
Old 01-11-2008
I'll instruct you despite your tone.
That's not an invalid memory location (your NULL pointer is a misleading term), it's a pointer to type char assigned NULL. There is a valid memory location assigned to this pointer but no additional storage has been allocated. Thus the assignment of NULL and the printing of the assignment is perfectly legal.
Code:
printf("Pointer at %p and value assigned =%s\n",&p,p);

Perhaps this is what you meant to say would segfault as it is a dereference.
Code:
printf("%c",*p);

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies

2. Programming

about core dump

MY friends: my program under sco unix have a problem? it create a core dump file on the path when execute program , but i can't find the error of the C program ,i don't know how to see the error about my program use core, please help me or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies

3. UNIX for Advanced & Expert Users

core dump

Hi All, i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know. sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies

4. UNIX for Dummies Questions & Answers

core dump file size

Hi All, is there any way to find out the optimal/would be size of the cor dump file generated by the system while a process got terminated abnormally? Basically we have been asked to provide the size of the core dump file being generated by the administrators who maintained the UNIX boxes.... (4 Replies)
Discussion started by: pushp.gahlot
4 Replies

5. AIX

core dump

My application gives core dump. When i am debugging with dbx getting instructions below: pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error) pthreaded.c, 1941: PTHDB_INTERNAL (internal error) Illegal instruction (illegal opcode) in . at 0x0 warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies

6. Programming

How to use a core dump file

Hi All, May be it is a stupid question, but, I would like to know what is the advantage using a core dump file at the moment of debugging using gdb. I know a core dump has information about the state of the application when it crashed, but, what is the difference between debugging using the... (2 Replies)
Discussion started by: lagigliaivan
2 Replies

7. Shell Programming and Scripting

Cannot generate core dump file

Segmentation fault(core dumped) but I cant find core file any where. how to make it out? I try the command:ulimit -c unlimited, I even added it to the .bashrc file.And I removed ulimit setting in /etc/init.d/function. And there's no ulimit setting in /etc/profile. And I tried sudo find /... (8 Replies)
Discussion started by: vistastar
8 Replies

8. UNIX for Dummies Questions & Answers

No core dump

my progrme complaints 'Segmentation fault'. How to let it print 'Segmentation fault(core dumped)' and generate core dump file? $ulimit unlimited (22 Replies)
Discussion started by: vistastar
22 Replies

9. Emergency UNIX and Linux Support

How to open the core dump file in linux?

Hi, I have got core dump stating "core.bash.29846" so i am unable to open. How to open the core dump file for further analysis? Reagards Vanitha (7 Replies)
Discussion started by: vanitham
7 Replies

10. Solaris

Problems in reading CORE DUMP file with dbx

I am new to UNIX. My Application is using c (.so files) and Java code. My application crashes and CORE DUMP file is generated ,which is huge. Now I want to view the CORE DUMP file to debug the application using dbx without starting process again. By only using the CORE DUMP file and dbx ,can i... (1 Reply)
Discussion started by: satde
1 Replies
savecore(8)						      System Manager's Manual						       savecore(8)

Name
       savecore - save a core dump of the operating system

Syntax
       /etc/savecore [ options ] dirname [ system ] [ corename ]

Description
       The  command  is  meant	to  be called near the end of the file.  The command saves the core dump of the system (assuming one was made) and
       writes a reboot message in the shutdown log.

       The command checks the core dump to be certain it corresponds with the current running ULTRIX.  If it does, it saves the core image in  the
       file  dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n.  The trailing .n in the pathnames is replaced by a number which
       increments each time is run in that directory.

       After saving the core and namelist images, will save the error logger buffer into a predetermined file.	The error logger  buffer  contains
       information about why the crash occurred.  After completes, the daemon will extract the error logger file and translate its contents into a
       form familiar to the program.

       Before writes out a core image, it reads a number from the file dirname/minfree.  If there are fewer free blocks  on  the  filesystem  that
       contains  dirname  than the number obtained from the file, a core dump is not done.  If the file does not exist, savecore always writes out
       the core file (assuming that a core dump was taken).

       The command also writes a reboot message in the shut down log.  If the system crashed as a result of a panic, also records the panic string
       in the shut down log.

       For  partial  crash  dumps,  creates  a	sparse	core image file in dirname/vmcore.n.  If this sparse core image file is copied or moved to
       another location, the file expands to its true size which can take too much file system space.  Hence, to copy or move  sparse  core  image
       files, you must use the command. The command has a conversion option to create sparse output files.

Options
       -c   Clears  the core dump.  This option is useful when the core dump is corrupted in a way that will not allow to save it safely.  Use the
	    option with caution, because once it clears the core dump, the core dump cannot be retrieved.

       -d dumpdev dumplo
	    Specifies the dump device and the dump offset when running on a system image other than the currently running system image.  The  pro-
	    gram  assumes  that  the running system image is and it reads the dump device and dump device offset are different in the system image
	    that crashed, the option provides the correct dump device and dump device offset.

       -e   Saves only the error logger buffer into a file.  If used, core or namelist images are not saved.

       -f corename
	    Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device.   This  option
	    is used only for diskless workstations.

       If  the	core  dump was from a system other than /vmunix, the name of that system must be supplied as system.  The program assumes that the
       running image is

       After successful completion, the core dump is cleared.  Also, a message is written in the file which tells whether the  dump  succeeded	or
       failed.

Files
       Shut down log

       Current running ULTRIX system

See Also
       dd(1), uerf(8)

																       savecore(8)
All times are GMT -4. The time now is 03:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy