pri queue manager/attached .erl file - spawned process exitin g
Fri Apr 19 17:45:45 CEST 2002
Vance has pointed out why your infinite recursion isn't working. On windows,
when you start an erlang shell, sasl isn't automatically started.
At the command line, start the sasl application
=CRASH REPORT==== 19-Apr-2002::16:49:39 ===
From: Sameer Pendse [mailto:sameerp@REDACTED]
Sent: 19 April 2002 15:22
To: Vance Shipley; Ulf Wiger; erlang-questions@REDACTED
Subject: pri queue manager/attached .erl file - spawned process exiting
i have attached qmpri.erl which implements priority message processing using
time-outs. same problem here is that the spawned process exits/dies quietly,
pman seems to indicate a badarg situation - but that is not getting thrown
3. qmpri:testdeq(Qm). % this just waits because pid=Qm has vanished
can you advise on why qmpri:qm/1 is quitting out of infinite recursion in
the absence of a stop message?
From: Vance Shipley [mailto:vances@REDACTED]
Sent: Friday, April 19, 2002 7:13 PM
To: Sameer Pendse
Cc: Ulf Wiger; erlang-questions@REDACTED
Subject: Re: no badarg thrown by spawned process - quiet ext
On Fri, 19 Apr 2002, Sameer Pendse wrote:
>in a spawned process, if i do a io:format("...~w",L) where L is
>a list, then my spawned process exits without a badarg error. if
>i put the L in a [L], it works fine. if i do the badop in a
>top-level process, i do get the badarg error.
Since the secord argument to io:format/2 is supposed to be a list
if you pass it a list as you say the behaviour will depend on what
is in that list. It may even work:
9> L = [foo].
10> io:format("...~w~n", L).
I tried a couple things and they all gave me a badarg.
What is in your list?
Motivity Telecom Inc.
+1 519 579 5816
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions