Sponsored Content
Full Discussion: Dealing with geany core
Special Forums UNIX and Linux Applications Dealing with geany core Post 302512200 by Corona688 on Friday 8th of April 2011 04:19:12 PM
Old 04-08-2011
It's not some sort of geany file, it's just the raw memory the program had when it crashed. Depending on your system you could use a debugger of some sort to open it and see what it's like inside, but its contents may not make any sense to you, especially if geany wasn't compiled with debugging support.

In short I think it's doubtful that you can retrieve any unsaved changes from this sort of crash dump. Save more often Smilie
 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help in dealing with arra

I am readinga file lin by line and based craeting a arry of unique elemenst from the second column of the line. However when i coem out of the while loop my array becomes empty , can eny one tell me what I would be doing wrong #!/bin/bash logfile="./mylog.dat" begin=100 end="$(( $begin +... (5 Replies)
Discussion started by: jojan
5 Replies

2. 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

3. Programming

Need help with Card Dealing Program

I'm currently making a card dealing program, it is suppose to display a list of cards like this: "Ace of Heart, is red" "Two of Heart, is red" . . "Ace of Spade, is black" and so on for all suits and numbers. here is my current code: #include <stdio.h> #include <stdlib.h> #include... (3 Replies)
Discussion started by: Izzy123
3 Replies

4. Shell Programming and Scripting

Dealing with multiple files

Korn Shell I have hundreds of small files like below created every day. A midnight cron job moves them to the location /u04/temp/logs But sometimes I have to manually move these files based a certain dates or time. I have two basic requirements 1.Using mv command I want to move all .dat... (2 Replies)
Discussion started by: kraljic
2 Replies

5. UNIX for Dummies Questions & Answers

Dealing with sum

I have file input 1/1/2013 1AS030A 0 1083 CHINA 1/1/2013 1AS030B 0 675 KOREA 1/1/2013 1AS035A 162 662 CHINA 1/1/2013 1AS035B 51 799 INDIA 1/1/2013 1AS035C 0 731 CHINA 1/2/2013 1AS073A 10 1375 KOREA... (5 Replies)
Discussion started by: radius
5 Replies
GCORE(1)						    BSD General Commands Manual 						  GCORE(1)

NAME
gcore -- get core images of running process SYNOPSIS
gcore [-f] [-s] [-c core] [executable] pid DESCRIPTION
The gcore utility creates a core image of the specified process, suitable for use with gdb(1). By default, the core is written to the file ``core.<pid>''. The process identifier, pid, must be given on the command line. The following options are available: -c Write the core file to the specified file instead of ``core.<pid>''. -f Dumps all available segments, excluding only malformed and undumpable segments. Unlike the default invocation, this flag dumps map- pings of devices which may invalidate the state of device transactions or trigger other unexpected behavior. As a result, this flag should only be used when the behavior of the application and any devices it has mapped is fully understood and any side effects can be controlled or tolerated. -s Stop the process while gathering the core image, and resume it when done. This guarantees that the resulting core dump will be in a consistent state. The process is resumed even if it was already stopped. The same effect can be achieved manually with kill(1). FILES
core.<pid> the core image HISTORY
A gcore utility appeared in 4.2BSD. BUGS
Because of the ptrace(2) usage gcore may not work with processes which are actively being investigated with truss(1) or gdb(1). Addition- ally, interruptable sleeps may exit with EINTR. The gcore utility is not compatible with the original 4.2BSD version. BSD
July 14, 2010 BSD
All times are GMT -4. The time now is 04:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy