• 0

[C] Segmentation fault: core dumped


Question

Could someone explain to me what a segmentation fault is, and what is causing it within my program? I'd be grateful for any help! :D

#include <stdio.h>
#define ARR 50

void Fill_Arrays(int ID[], int max, double score[], int *count);
double average(const int score[], int count1);

int main (void)
{
FILE *outp;
outp = fopen("output.out", "w");
int ID[ARR], count = 0, input_status;
double score[ARR], av;
Fill_Arrays(ID, ARR, score, &count);
av= average(score[], count);
fclose(outp);
return (0);
}


void Fill_Arrays (int ID[], int max, double score[], int *count)
{
FILE *inp;
int input_status, data1;
double data2;
inp = fopen("assignment8.dat", "r");
input_status= fscanf(inp, "%d%lf", data1, data2);
while (input_status != EOF && *count < max){
ID[*count] = data1;
score[*count] = data2;
*count++;
input_status= fscanf(inp, "%d&lf", data1, data2);
}
fclose(inp);
}

double average(const int score[], int count1)
{
int counter;
double sum=0, average;
for (counter = 0; counter <= count1; counter++)
sum+=score[counter];
average=sum/count1;
return (average);
}

Edited by togamonkey
Link to comment
https://www.neowin.net/forum/topic/327665-c-segmentation-fault-core-dumped/
Share on other sites

3 answers to this question

Recommended Posts

  • 0

It's in your Fill_Arrays function. fscanf expects pointers, you're giving it the values inside your variables instead, thus causing a seg fault. You should also check before you use FILE* inp that inp is not NULL. You've also got some errors in switching between data types. Look over this program again and I bet you'll spot some of your errors.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This is the curse of Linux on the desktop, the development and maintenance manpower is spread out across countless distributions. The same thing has to be integrated many times.
    • The new official logo of the GOP
    • Linux 6.16-rc1 is out: What's new and what does it mean for your system? by Paul Hill Linus Torvalds, head and founder of the Linux kernel, has announced the closure of the merge window where major new features are added to the kernel, and the beginning of the Linux 6.16 release candidates, beginning with release candidate 1 (Linux 6.16-rc1). Linux 6.15 was released two weeks ago and in the time since, developers have had the opportunity to try and get their new kernel features into the Linux 6.16 kernel. Over the next two months, we will get seven or eight release candidates where developers will stabilize new and existing features. This means that the stable version of Linux 6.16 will arrive around the end of July. Torvalds said that the merge window seemed pretty normal this time, but did say he had a feeling that there were more “late straggler” pull requests than is typical. Despite this, everything seems to be fine and the schedule will be going forward as planned. Key areas of development Torvalds explained that around half of the changes in the first release candidate were driver updates, with the bulk of those being made up with by GPU and networking drivers. For end users these are the most important changes because when your favorite distribution of Linux ships a new release with this kernel, it will support more graphics cards and networking equipment like Wi-Fi cards. The non-driver updates in this version are split between architecture-specific updates, documentation and tooling (perf tool and selftests), and core changes to filesystems, core kernel, memory management, and networking. Torvalds said the core changes include some of the “most important” changes, though they’re not necessarily major changes. Fixes to the core ensure a more stable Linux kernel for end users, plus better performance. The merge window saw developers submit thousands of non-merge commits and merges. The non-merge commits were around 13,000 while the merge commits nearly reached 1,000. There were 1,783 unique authors submitting code during this window. Next steps Over the coming weeks, Linux developers, including individuals or representatives of companies, will submit bug fixes for new and existing features. This release candidate cycle will run until around the end of July and then the final version will become available. End users shouldn’t go out and download Linux 6.16 when it’s released, instead just wait for your Linux distribution to update to it, as distribution-specific changes get made. Neowin will be following these releases and reporting on any interested changes that are noted. Source: LKML
    • There was no cancelation. Microsoft delayed work on it to focus on further tuning the OS and improving the OS experience overall, before going full core into a direct hardware battle with their partners.
  • Recent Achievements

    • Week One Done
      Al_ earned a badge
      Week One Done
    • Week One Done
      MadMung0 earned a badge
      Week One Done
    • Reacting Well
      BlakeBringer earned a badge
      Reacting Well
    • Reacting Well
      Lazy_Placeholder earned a badge
      Reacting Well
    • Dedicated
      Epaminombas earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +FloatingFatMan
      273
    3. 3
      ATLien_0
      242
    4. 4
      snowy owl
      211
    5. 5
      Edouard
      182
  • Tell a friend

    Love Neowin? Tell a friend!