Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In this line:</p> <pre><code>struct node*p; </code></pre> <p>it should be</p> <pre><code>struct node p; </code></pre> <p>you're creating pointer to node. But don't initialize it later, so no node is created and it points to random location. Then you pass that as argument to your functions.<br> When you are dereferencig this pointer in your functions <code>p-&gt;</code> you have a segmentation fault. <br><br> In your <code>main</code> function you should have declaration of 'node', not <code>pointer to node</code>, and then pass node's address to function with <code>&amp;</code> operator.<br><br> So your function declaration <code>void addatbeg(struct node *p,int num);</code> is fine but it should be called (after you declare node p):</p> <pre><code>addatbeg(&amp;p,some_number); </code></pre> <p>Also, every function that makes use of p should be changed to treat p like a structure, not like pointer to structure.<br><br> What you did here is confused some information on linked lists.<br> Usually head of a <code>singly linked list</code> declared as a pointer to node. When I implemented sll myself I did that, too. Then you pass that pointer by reference to functions manipulating on linked list and it works fine.<br> On the other hand you got <code>doubly linked lists</code>, and there it is more convinient to treat head of <code>doubly linked list</code> as just another node, but without value.<br> You are trying to mix those ideas together without understanding ideas behind them. <br> I gave you bunch of tips on how to make it work, but fixing it would mean that I have to rewrite your whole code.<br><br> And that's not the point since you should learn it yourself.</p>
    singulars
    1. This table or related slice is empty.
    1. POLinked List Implementation in C - Segmentation fault error
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USzubergu
    1. USzubergu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POLinked List Implementation in C - Segmentation fault error
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COIts still giving `segmetation fault`.
      singulars
      1. PO
      1. USInsane Coder
    2. COYou need to make the corresponding changes to the other routines - display, count, etc. or the same thing will happen there as well.
      singulars
      1. PO
      1. USDavid W
    3. COI don't think it is a good idea to have one list element on the stack and the rest on the heap. If you add some elements at the beginning and some at the hand, how would you know which element not to free? Additionally this element gets lost when the function it is defined in ends.
      singulars
      1. PO
      1. USebo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload