Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Thread parameter in ANSI C makes a segmentation fault
Top Forums Programming Thread parameter in ANSI C makes a segmentation fault Post 302520028 by Loic Domaigne on Thursday 5th of May 2011 03:54:43 PM
Old 05-05-2011
Quote:
Originally Posted by sehang
Thanks. I try it now. However, I can run the program under the text mode only since our system doesn't have a GUI. Is valgrind able to work in text mode?
Yes, valgrind work in text mode. Which processor architecture are you using?

Could you run the following command under gdb:
Code:
thread apply all bt

Besides that, I am a bit surprised by the "signal 6". You mentioned SIGSEGV, and I believe that would be always 11 on Linux? Perhaps you are looking at the wrong place...

Cheers, Loïc
 

10 More Discussions You Might Find Interesting

1. Programming

Hi! segmentation fault

I have written a program which takes a directory as command line arguments and displays all the dir and files in it. I don't know why I have a problem with the /etc directory.It displays all the directories and files untill it reaches a sub directory called peers which is in /etc/ppp/peers.the... (4 Replies)
Discussion started by: vijlak
4 Replies

2. Programming

segmentation fault

ive written my code in C for implementation of a simple lexical analyser using singly linked list hence am making use of dynamic allocation,but when run in linux it gives a segmentation fault is it cause of the malloc function that ive made use of????any suggestions as to what i could do??? thank... (8 Replies)
Discussion started by: rockgal
8 Replies

3. AIX

Segmentation fault

Hi , During execution a backup binary i get following error "Program error 11 (Segmentation fault), saving core file in '/usr/datatools" Riyaz (2 Replies)
Discussion started by: rshaikh
2 Replies

4. Programming

segmentation fault

If I do this. Assume struct life { char *nolife; } struct life **life; // malloc initialization & everything if(life->nolife == 0) Would I get error at life->nolife if it is equal to 0. wrong accession? (3 Replies)
Discussion started by: joey
3 Replies

5. Programming

segmentation fault.

This code is causing a segmentation fault and I can't figure out why. I'm new to UNIX and I need to learn how to avoid this segmentation fault thing. Thank you so much. Thanks also for the great answers to my last post.:):b: int main() { mysqlpp::Connection conn(false); if... (3 Replies)
Discussion started by: sepoto
3 Replies

6. Programming

Segmentation fault in C

i have this code int already_there(char *client_names, char *username) { int i; for(i = 0; i<NUM; i++) { printf("HERE\n"); if (strcmp(client_names, username)==0) return(1); } return(0); } and i get a segmentation fault, whats wrong here? (7 Replies)
Discussion started by: omega666
7 Replies

7. UNIX for Advanced & Expert Users

segmentation fault with ps

What does this mean and why is this happening? $ ps -ef | grep ocular Segmentation fault (core dumped) $ ps -ef | grep ocular Segmentation fault (core dumped) $ ps aux | grep ocular Segmentation fault (core dumped) $ ps Segmentation fault (core dumped) $ pkill okular $ ps... (1 Reply)
Discussion started by: cokedude
1 Replies

8. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this : i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies

9. Programming

Segmentation fault

I keep getting this fault on a lot of the codes I write, I'm not exactly sure why so I'd really appreciate it if someone could explain the idea to me. For example this code #include <stdio.h> main() { unsigned long a=0; unsigned long b=0; int z; { printf("Enter two... (2 Replies)
Discussion started by: sizzler786
2 Replies

10. Programming

C. To segmentation fault or not to segmentation fault, that is the question.

Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1... I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one. Below are two very condensed snippets of which I have added the results inside the each code section. IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies

LEARN ABOUT OPENDARWIN

callgrind_control

CALLGRIND 
CONTROL(1)						   Release 3.7.0					      CALLGRIND CONTROL(1)

NAME

       callgrind_control - observe and control programs being run by Callgrind

SYNOPSIS

       callgrind_control [options] [pid|program-name...]

DESCRIPTION

       callgrind_control controls programs being run by the Valgrind tool Callgrind. When a pid/program name argument is not specified, all
       applications currently being run by Callgrind on this system will be used for actions given by the specified option(s). The default action
       is to give some brief information about the applications being run by Callgrind.

OPTIONS

       -h --help
	   Show a short description, usage, and summary of options.

       --version
	   Show version of callgrind_control.

       -l --long
	   Show also the working directory, in addition to the brief information given by default.

       -s --stat
	   Show statistics information about active Callgrind runs.

       -b --back
	   Show stack/back traces of each thread in active Callgrind runs. For each active function in the stack trace, also the number of
	   invocations since program start (or last dump) is shown. This option can be combined with -e to show inclusive cost of active
	   functions.

       -e [A,B,...]  (default: all)
	   Show the current per-thread, exclusive cost values of event counters. If no explicit event names are given, figures for all event types
	   which are collected in the given Callgrind run are shown. Otherwise, only figures for event types A, B, ... are shown. If this option
	   is combined with -b, inclusive cost for the functions of each active stack frame is provided, too.

       --dump[=<desc>]	(default: no description)
	   Request the dumping of profile information. Optionally, a description can be specified which is written into the dump as part of the
	   information giving the reason which triggered the dump action. This can be used to distinguish multiple dumps.

       -z --zero
	   Zero all event counters.

       -k --kill
	   Force a Callgrind run to be terminated.

       --instr=<on|off>
	   Switch instrumentation mode on or off. If a Callgrind run has instrumentation disabled, no simulation is done and no events are
	   counted. This is useful to skip uninteresting program parts, as there is much less slowdown (same as with the Valgrind tool "none").
	   See also the Callgrind option --instr-atstart.

       -w=<dir>
	   Specify the startup directory of an active Callgrind run. On some systems, active Callgrind runs can not be detected. To be able to
	   control these, the failed auto-detection can be worked around by specifying the directory where a Callgrind run was started.

SEE ALSO

       valgrind(1), $INSTALL/share/doc/valgrind/html/index.html or http://www.valgrind.org/docs/manual/index.html.

AUTHOR

       Josef Weidendorfer <Josef.Weidendorfer@gmx.de>.

Release 3.7.0							    06/05/2012						      CALLGRIND CONTROL(1)
All times are GMT -4. The time now is 11:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy