|
|
Sponsored Content
Top Forums
Programming
Multithreading in Pro*C
Post 10558 by rwb1959 on Friday 16th of November 2001 08:44:32 AM
11-16-2001
dbx should work for you. You can even
execute the program via dbx and set break points
to allow you to step through the segment of code
and "watch" the variable in question. However,
multithreaded programs tend to be more difficult
to "step" through and in many cases that I have
observed personally, the code will not fail
when executed from the debugger
I would recommend a couple of things...
I would first add signal handling to catch
the signal (I assume you are getting a SEGV or
Segmentation fault type of error). This will
at least allow you to "control" the fault
detection to allow your program to "clean up"
then you can all "abort()" to dump a core image
if you like. Also, I would go to the
"old fashioned" way of what I like to call
"brute force" debugging. I would add logging
code around the sections of code that assign
values to this variable (be sure to "flush()" the
output to the log before moving on to the next
statement). Also, make sure that the Oracle
libraries and any shared libraries that you use
on the production machine are the same version
as your development environment.
Another thing to try, is if you can build the
code completely with "static" libraries, do that.
It may also help to post the "exact" system
error message. I assuming it's a SEGV error
which typically indicates stack corruption which
can easily happen if the bounds of an array are
exceeded but seeing the error would verify this
assumption.
execute the program via dbx and set break points
to allow you to step through the segment of code
and "watch" the variable in question. However,
multithreaded programs tend to be more difficult
to "step" through and in many cases that I have
observed personally, the code will not fail
when executed from the debugger
I would recommend a couple of things...
I would first add signal handling to catch
the signal (I assume you are getting a SEGV or
Segmentation fault type of error). This will
at least allow you to "control" the fault
detection to allow your program to "clean up"
then you can all "abort()" to dump a core image
if you like. Also, I would go to the
"old fashioned" way of what I like to call
"brute force" debugging. I would add logging
code around the sections of code that assign
values to this variable (be sure to "flush()" the
output to the log before moving on to the next
statement). Also, make sure that the Oracle
libraries and any shared libraries that you use
on the production machine are the same version
as your development environment.
Another thing to try, is if you can build the
code completely with "static" libraries, do that.
It may also help to post the "exact" system
error message. I assuming it's a SEGV error
which typically indicates stack corruption which
can easily happen if the bounds of an array are
exceeded but seeing the error would verify this
assumption.
|
|
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
LEARN ABOUT FREEBSD
kgdb
KGDB(1) BSD General Commands Manual KGDB(1) NAME
kgdb -- kernel debugger SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]] DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files. The options are as follows: -a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well. -b rate Set the baudrate to rate. -q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well. -v Increase verbosity. -w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for FreeBSD.) -d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will be appended to determine the actual dump file name. -c core Explicitly use core as the core dump file. -n dumpnr Use the kernel core dump file numbered dumpnr for debugging. -r device Use device to connect kgdb to for a remote debugging session. The -c, -n, and -r options are mutually exclusive. Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu- ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run- ning kernel. FILES
/dev/mem Default memory image to open if no core dump file has been specified. /var/crash Default directory to locate kernel core dump files. SEE ALSO
gdb(1) HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3. BSD
October 11, 2006 BSD