Sponsored Content
Top Forums Programming Why not a segmentation fault?? Post 302193115 by lagigliaivan on Thursday 8th of May 2008 02:26:50 PM
Old 05-08-2008
Thanks!

Hi All,

Certainly I'm fixing an application with this type of code and I've replaced the sprintf by snprintf function, but I have to explain to my boss why I'm doing it and I need to show him the application crashing.

The original message in the printf function overcomes the boundaries only for 2 bytes and it doesn't crash, I don't know how to do it and I don't know if its behavior is deterministic or not.

Thanks to all of you for your support!!!!!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Segmentation Fault

hello all, I tried a program on an array to intialise array elements from the standard input device.it is an integer array of 5 elements.but after entering the 4th element it throws a message called "Segmentation Fault" and returns to the command prompt without asking for the 5th element. ... (3 Replies)
Discussion started by: compbug
3 Replies

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

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

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

5. UNIX for Dummies Questions & Answers

Segmentation Fault

Hi, While comparing primary key data of two tables thr bteq script I am getting this Error. This script is a shell script. *** Error: The following error was encountered on the output file. Script.sh: 3043492 Segmentation fault(coredump) Please let me know how to get through it. ... (5 Replies)
Discussion started by: monika
5 Replies

6. Programming

segmentation fault

Hi, I am having this segmentation fault not in the following program, bt. in my lab program . My lab program is horrible long so cannot post it here bt. I am using the following logic in my program which is giving the segmentation fault. Bt. if I run this sample program as it is it dosen't give... (3 Replies)
Discussion started by: mind@work
3 Replies

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

8. Homework & Coursework Questions

Segmentation Fault

this is a network programming code to run a rock paper scissors in a client and server. I completed it and it was working without any error. After I added the findWinner function to the server code it starts giving me segmentation fault. -the segmentation fault is fixed Current problem -Also... (3 Replies)
Discussion started by: femchi
3 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
explain_snprintf(3)					     Library Functions Manual					       explain_snprintf(3)

NAME
explain_snprintf - explain snprintf(3) errors SYNOPSIS
#include <libexplain/snprintf.h> const char *explain_snprintf(char *data, size_t data_size, const char *format); const char *explain_errno_snprintf(int errnum, char *data, size_t data_size, const char *format); void explain_message_snprintf(char *message, int message_size, char *data, size_t data_size, const char *format); void explain_message_errno_snprintf(char *message, int message_size, int errnum, char *data, size_t data_size, const char *format); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the snprintf(3) system call. explain_snprintf const char *explain_snprintf(char *data, size_t data_size, const char *format); The explain_snprintf function is used to obtain an explanation of an error returned by the snprintf(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. data The original data, exactly as passed to the snprintf(3) system call. data_size The original data_size, exactly as passed to the snprintf(3) system call. format The original format, exactly as passed to the snprintf(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. Example: This function is intended to be used in a fashion similar to the following example: errno = 0; int result = snprintf(data, data_size, format); if (result < 0 && errno != 0) { fprintf(stderr, "%s ", explain_snprintf(data, data_size, format)); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_snprintf_or_die(3) function. explain_errno_snprintf const char *explain_errno_snprintf(int errnum, char *data, size_t data_size, const char *format); The explain_errno_snprintf function is used to obtain an explanation of an error returned by the snprintf(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. data The original data, exactly as passed to the snprintf(3) system call. data_size The original data_size, exactly as passed to the snprintf(3) system call. format The original format, exactly as passed to the snprintf(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. Example: This function is intended to be used in a fashion similar to the following example: errno = 0; int result = snprintf(data, data_size, format); if (result < 0 && errno != 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_snprintf(err, data, data_size, format)); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_snprintf_or_die(3) function. explain_message_snprintf void explain_message_snprintf(char *message, int message_size, char *data, size_t data_size, const char *format); The explain_message_snprintf function is used to obtain an explanation of an error returned by the snprintf(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. data The original data, exactly as passed to the snprintf(3) system call. data_size The original data_size, exactly as passed to the snprintf(3) system call. format The original format, exactly as passed to the snprintf(3) system call. Example: This function is intended to be used in a fashion similar to the following example: errno = 0; int result = snprintf(data, data_size, format); if (result < 0 && errno != 0) { char message[3000]; explain_message_snprintf(message, sizeof(message), data, data_size, format); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_snprintf_or_die(3) function. explain_message_errno_snprintf void explain_message_errno_snprintf(char *message, int message_size, int errnum, char *data, size_t data_size, const char *format); The explain_message_errno_snprintf function is used to obtain an explanation of an error returned by the snprintf(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. data The original data, exactly as passed to the snprintf(3) system call. data_size The original data_size, exactly as passed to the snprintf(3) system call. format The original format, exactly as passed to the snprintf(3) system call. Example: This function is intended to be used in a fashion similar to the following example: errno = 0; int result = snprintf(data, data_size, format); if (result < 0 && errno != 0) { int err = errno; char message[3000]; explain_message_errno_snprintf(message, sizeof(message), err, data, data_size, format); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_snprintf_or_die(3) function. SEE ALSO
snprintf(3) formatted output conversion explain_snprintf_or_die(3) formatted output conversion and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2010 Peter Miller explain_snprintf(3)
All times are GMT -4. The time now is 04:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy