09-22-2001
I think the first thing you want to do is to
examine the core file using a debugger. The
debugger you use will depend on the compiler
tools you are using. For instance, if you are
using gcc/g++ you can debug using gdb. Using
gdb, you can load the program executable
along with the core file and run the "bt"
(backtrace) command to find exactly where the
program is failing. It would be better to have
the program compiled using the "-g" (for gcc)
option so that a symbol table is created so you
can follow the program execution in a very
detailed manner.
If you are not using the GNU compiler/debugger
then you'll have to find out what debugger
you have on your system (i.e. ladebug, dbx, sdb,
adb, etc...)
On increasing the stack size, you will have to
check your compiler documentation as this is
very compiler dependent.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
this is the seventh problem i'm having with samba.
for some reason, i cannot logon to the domain.
i've created user accounts... and i was able to establish a connection between
the samba server (my PDC) and my workstations by logging in as "root."
however now when i try to logon it gives... (5 Replies)
Discussion started by: xyyz
5 Replies
2. Programming
Hi all, I have a query about multithreading. What I would like to do is, at the start of my main update() function, start a couple of threads in parallel, once they are all complete carry on with my main update function.
void update() {
thread1->update(); // fluid solver
... (3 Replies)
Discussion started by: memoid
3 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I am new to this forum and this is my first post here...
I have never worked on either Pro*C or Multithreading..Now, i have to write a Pro*C, Multithreading daemon process.. I dont know where to start.. Can anybody help me with examples?
1. need to write a Pro*C multithreading... (0 Replies)
Discussion started by: kachiraju
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
Can you please give me a suitable reference to learn multithreading programming in C in UNIX?
Thanks (3 Replies)
Discussion started by: naan
3 Replies
5. Shell Programming and Scripting
Hi
I need to insert 1million records into MySQL database, but it is taking lot of time as there is no bulk insert support.
I want to spawn 10 processes which will insert 100k records each parallely.
Can somebody help me with a example program to execute this task through shell scripting. (5 Replies)
Discussion started by: sach_roger
5 Replies
6. Programming
Situation:
i have multiple pthread_create calls like this:
pthread_create(...., ThreadFunc1,.....);
pthread_create(...., ThreadFunc2,.....);
.
.
which i am using to create multiple threads.All the "ThreadFunc<i>" functions are actually calling same function "Receive" of a class using same... (3 Replies)
Discussion started by: Sastra
3 Replies
7. IP Networking
hello to all
i want to use multithreading to my UDP broadcast server client program. will anyone help me by proving C code. i am working in fedora. also my requirement is POSIX compliance.please help me..... (0 Replies)
Discussion started by: moti12
0 Replies
8. Programming
hello to all
i want to use multithreading to my UDP broadcast server client program. will anyone help me by proving C code. i am working in fedora. also my requirement is POSIX compliance.please help me..... (6 Replies)
Discussion started by: moti12
6 Replies
9. Programming
I take this question of the The Linux Programming Interface: A Linux and Unix System Programming page 652 exercise 30.1
I want someone to explain the under line statement because it sounds complex to me couldn't understand anything
30-1 Modify the program (thread_incr.c) so that each loop in... (3 Replies)
Discussion started by: fwrlfo
3 Replies
GCORE(1) GNU Development Tools GCORE(1)
NAME
gcore - Generate a core file of a running program
SYNOPSIS
gcore [-o filename] pid
DESCRIPTION
Generate a core dump of a running program with process ID pid. Produced file is equivalent to a kernel produced core file as if the
process crashed (and if "ulimit -c" were used to set up an appropriate core dump limit). Unlike after a crash, after gcore the program
remains running without any change.
OPTIONS
-o filename
The optional argument filename specifies the file name where to put the core dump. If not specified, the file name defaults to
core.pid, where pid is the running program process ID.
SEE ALSO
The full documentation for GDB is maintained as a Texinfo manual. If the "info" and "gdb" programs and GDB's Texinfo documentation are
properly installed at your site, the command
info gdb
should give you access to the complete manual.
Using GDB: A Guide to the GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch, July 1991.
COPYRIGHT
Copyright (c) 1988-2013 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with the Invariant Sections being "Free Software" and "Free Software Needs
Free Documentation", with the Front-Cover Texts being "A GNU Manual," and with the Back-Cover Texts as in (a) below.
(a) The FSF's Back-Cover Text is: "You are free to copy and modify this GNU Manual. Buying copies from GNU Press supports the FSF in
developing GNU and promoting software freedom."
gdb-Red Hat Enterprise Linux 7.6.1-51.el7 2014-06-10 GCORE(1)