|Message: Re: Segmentation fault(core dumped)||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Segmentation fault indicates that you tried to access memory you didnt have access to. Typically by dereferencing a pointer that didnt point to what you thought it did. I suggest first trying gdb to try and find where it occured.
The coredump caused a file. Often called core (may have process numbers appended)
$ gdb ./program corefile
You will hopefully see a list of function names. The one at the top is where the segmentation fault occured.
If debug information was on at compile time you may even see something about what line it occured on. If not, then you then should go back to your strategy of using G4cout to narrow it down.
|Inline Depth:||Outline Depth:||Add message:|