StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13461939
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-19T20:47:14.690
FavoriteCount
0
LastActivityDate
2012-11-19T20:47:14.690
LastEditDate
LastEditorUserId
0
OwnerUserId
1217269
ParentId
13459190
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I think the reason can be found from the source code 'stdlib-1.18.2/src/shell.erl'. <pre><code>get_command(Prompt, Eval, Bs, RT, Ds) -> Parse = fun() -> exit(io:parse_erl_exprs(Prompt)) end, Pid = spawn_link(Parse), get_command1(Pid, Eval, Bs, RT, Ds). get_command1(Pid, Eval, Bs, RT, Ds) -> receive {'EXIT', Pid, Res} -> {Res, Eval}; {'EXIT', Eval, {Reason,Stacktrace}} -> report_exception(error, {Reason,Stacktrace}, RT), get_command1(Pid, start_eval(Bs, RT, Ds), Bs, RT, Ds); {'EXIT', Eval, Reason} -> report_exception(error, {Reason,[]}, RT), get_command1(Pid, start_eval(Bs, RT, Ds), Bs, RT, Ds) end. report_exception(Class, Reason, RT) -> report_exception(Class, serious, Reason, RT). report_exception(Class, Severity, {Reason,Stacktrace}, RT) -> Tag = severity_tag(Severity), I = iolist_size(Tag) + 1, PF = fun(Term, I1) -> pp(Term, I1, RT) end, SF = fun(M, _F, _A) -> (M =:= erl_eval) or (M =:= ?MODULE) end, io:requests([{put_chars, Tag}, {put_chars, lib:format_exception(I, Class, Reason, Stacktrace, SF, PF)}, nl]). start_eval(Bs, RT, Ds) -> Self = self(), Eval = spawn_link(fun() -> evaluator(Self, Bs, RT, Ds) end), %%<========start a new shell pid put(evaluator, Eval), Eval. severity_tag(fatal) -> <<"*** ">>; severity_tag(serious) -> <<"** ">>; severity_tag(benign) -> <<"* ">>. </code></pre> For your first case (sending message to self()), the signal meets the 2nd situation of <code>get_command1/5</code>, it will give error message firstly, and spawn a new shell pid. Please pay attention to <code>start_eval</code> function. For your second case (sending message to a spawn <code>pid</code>), Going back to your first part of post about the <code>exit</code> function, it is logical. Your spawned <code>pid</code> doesn't trap the exit message, and ignore the <code>(normal) exit</code> message. so the <code>shell</code> will receive exit message only when your spawn <code>pid</code>'s actual exit. It will go to the 1st condition of <code>get_command1/5</code>. Because <code>start_evel</code> is not been called, <code>shell pid</code> will keep the same. For your third case, I don't know why. I also think <code>is_process_alive(v(8))</code> should return true.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POErlang exit/2 bug in R15B03
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChen Yu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.