From gunilla@REDACTED Wed May 2 08:25:42 2007 From: gunilla@REDACTED (Gunilla Arendt) Date: Wed, 02 May 2007 08:25:42 +0200 Subject: [erlang-bugs] trivial typo bug in reference manual, section 12.3 "code replacement" In-Reply-To: <17973.226.670338.673217@antilipe.corelatus.se> References: <17973.226.670338.673217@antilipe.corelatus.se> Message-ID: <46382EE6.1090108@erix.ericsson.se> Fixed! Thanks, Gunilla, Erlang/OTP team Matthias Lang wrote: > The third paragraph reads > > "Bot old and current code is valid, and may be evaluated concurrently." > > The first word should be "Both". > > Matthias > _______________________________________________ > erlang-bugs mailing list > erlang-bugs@REDACTED > http://www.erlang.org/mailman/listinfo/erlang-bugs > From ulf.wiger@REDACTED Thu May 3 10:58:36 2007 From: ulf.wiger@REDACTED (Ulf Wiger (TN/EAB)) Date: Thu, 3 May 2007 10:58:36 +0200 Subject: [erlang-bugs] xmerl and standard HTML entity refs Message-ID: <6616D98C65DD514BA2E1DDC5F922315501C24C26@esealmw115.eemea.ericsson.se> I just noticed that xmerl_scan only recognizes the very limited set of entity references that I coded for back in 2000. (-: (This limited set happens to be the only predefined entity refs in the XML 1.0 standard, so that isn't a bug per se.) Is there any plan to include recognition of standard HTML entity refs, such as nbsp, iexcl, pound, frac14, etc.? 16> edoc:file("exprecs.erl"). 2670- fatal: {unknown_entity_ref,nbsp} 2580- fatal: error_scanning_entity_ref exprecs.erl, in module header: at line 28: error in XML parser: {fatal, {error_scanning_entity_ref, {file,file_name_unknown}, {line,86}, {col,18}}}. ** exited: error ** I realize that xmerl can be customized with a rules function which, for example, can handle entity references, but in this case, I was kinda hoping that edoc would allow me to use some standard HTML entity refs, and it currently doesn't. I think edoc should handle the standard HTML entity references. One way to do this is to extend xmerl to handle them, perhaps through a special XHTML parsing function. BR, Ulf W -------------- next part -------------- An HTML attachment was scrubbed... URL: From rickard.s.green@REDACTED Fri May 4 17:53:22 2007 From: rickard.s.green@REDACTED (Rickard Green) Date: Fri, 04 May 2007 17:53:22 +0200 Subject: [erlang-bugs] Missing the tcp_closed event In-Reply-To: <008BBA30-4E36-4F73-8032-8FE58629B2E2@process-one.net> References: <81631994-506C-4D80-93D2-BC125FF851E0@process-one.net> <948C5676-9293-4719-9C56-0A3BFA303694@process-one.net> <008BBA30-4E36-4F73-8032-8FE58629B2E2@process-one.net> Message-ID: <463B56F2.5020300@ericsson.com> Sorry for the late answer (the pipe has been full). Strictly speaking, the missing tcp_closed message is not a bug, and this behavior is not a new thing. gen_tcp has behaved like this for a very long time (if not always, at least since R7B). Why not a bug? If you change the active state from false to once after the socket has gone into a closed state and after you have been informed about this, i.e., send has returned {error, closed}, you won't get a tcp_closed message. This since you will only be informed once, and you have already been informed that the socket has been closed (informed the "active false way"). Unfortunately, sending on a socket on windows that has been closed in the other end will eventually cause gen_tcp:send to return {error, econnaborted} (where we got {error, closed} on unix). If you after that change active state from false to once, you will get a tcp_closed message. This because the socket had not been set into a closed state during the gen_tcp:send call. However, we can understand that one might expect a tcp_closed message as you did and that it would make active once easier to use. The different behaviors on windows and unix are also unfortunate. We will have a closer look at these problems and plan to do something about both problems. This will probably make it into R11B-5. Regarding the behavior of gen_tcp:send. gen_tcp:send may succeed even if the other end has closed. If the inet driver succeeds with the send operation, then gen_tcp:send will succeed. This doesn't imply that the other end has received the data, only that it has been buffered in the local tcp send buffer. BR, Rickard Green, Erlang/OTP, Ericsson AB. Micka?l R?mond wrote: > Hello, > > Can this problem be reproduced by your side ? > Do you need more informations ? > > Le 13 avr. 07 ? 18:23, Micka?l R?mond a ?crit : > >> Hello, >> >> Alexey managed to find the steps to reproduced the problem. >> You can have a process managing a TCP connection linked to a dead >> socket under the following conditions. >> >> 0. Use active once to receive your TCP message to benefit from TCP >> regulation >> 1. Assume we have a socket in {Active, false} state >> 2. Close its connection from the other end >> 3. call gen_tcp:send on the socket two times (It returns ok on the >> first send, which is also wrong. The problem happens only with two or >> more sends). >> 4. swith to {active, once} state >> => no {tcp_closed, ...} message is received by the process. >> >> If you check the state of your port after step 4 (for example with >> inet:peername) you will receive an error enotconn. >> >> You end up with a stuck process. If you send messages to the process >> queue to send messages on the socket it will accumulate indefinitely. >> >> Please, let me know if we can do something more to help. >> >> -- >> Micka?l R?mond >> http://www.process-one.net/ >> >> >> >> _______________________________________________ >> erlang-bugs mailing list >> erlang-bugs@REDACTED >> http://www.erlang.org/mailman/listinfo/erlang-bugs > > -- > Micka?l R?mond > http://www.process-one.net/ > > > > ------------------------------------------------------------------------ > > _______________________________________________ > erlang-bugs mailing list > erlang-bugs@REDACTED > http://www.erlang.org/mailman/listinfo/erlang-bugs From matthias@REDACTED Tue May 8 19:43:26 2007 From: matthias@REDACTED (Matthias Radestock) Date: Tue, 08 May 2007 18:43:26 +0100 Subject: [erlang-bugs] erl_syntax:type/1 fails for binary comprehensions In-Reply-To: (Matthias Radestock's message of "Fri, 13 Apr 2007 20:20:42 +0100") References: Message-ID: Matthias Radestock writes: > The code in erl_syntax:type/1 is missing a case for the bc (binary > comprehension) nodes produced by erl_parse. Any idea when this will be fixed? Regards, Matthias. From matthias@REDACTED Tue May 8 19:58:05 2007 From: matthias@REDACTED (Matthias Radestock) Date: Tue, 08 May 2007 18:58:05 +0100 Subject: [erlang-bugs] mnesia dir not always created automatically Message-ID: Mnesia usually creates the specified mnesia directory when that does not yet exists. However, I have found one scenario where that doesn't happen and mnesia crashes instead. Here's the code: -module(mnesiatest). -export([start_master/0, start_slave/1]). start_master() -> ok = mnesia:create_schema([node()]), ok = mnesia:start(). start_slave(MasterNode) -> ok = mnesia:start(), {ok, [MasterNode]} = mnesia:change_config(extra_db_nodes, [MasterNode]), mnesia:change_table_copy_type(schema, node(), disc_copies), halt(). and here is a transcript showing the problem: $ mkdir /tmp/mnesiatest $ erl -sname foo -mnesia dir '"/tmp/mnesiatest/foo"' -noshell -noinput -eval 'mnesiatest:start_master()' & [1] 29026 $ erl -sname bar -mnesia dir '"/tmp/mnesiatest/bar"' -noshell -eval 'mnesiatest:start_slave(foo@REDACTED)' $ rm /tmp/mnesiatest/bar/* $ erl -sname bar -mnesia dir '"/tmp/mnesiatest/bar"' -noshell -eval 'mnesiatest:start_slave(foo@REDACTED)' $ rm /tmp/mnesiatest/bar/* $ rmdir /tmp/mnesiatest/bar $ erl -sname bar -mnesia dir '"/tmp/mnesiatest/bar"' -noshell -eval 'mnesiatest:start_slave(foo@REDACTED)' Mnesia(bar@REDACTED): Data may be missing, Corrupt logfile deleted: "/tmp/mnesiatest/bar/LATEST.LOG", {file_error, "/tmp/mnesiatest/bar/LATEST.LOG", enoent} =ERROR REPORT==== 8-May-2007::18:37:31 === Mnesia(bar@REDACTED): ** ERROR ** (core dumped to file: "/home/rade/experiments/erlang/MnesiaCore.bar@REDACTED") As you can see, mnesia quite happily creates a directory for the master node and a directory for the slave node the first time it is started. The slave note restarts fine after its mnesia directory *contents* have been wiped out. However, deleting the directory itself results in a crash. This is happening in R11B-4. I haven't tested earlier versions. Regards, Matthias From horndude77@REDACTED Thu May 10 06:04:17 2007 From: horndude77@REDACTED (Jay Anderson) Date: Thu, 10 May 2007 04:04:17 +0000 (UTC) Subject: [erlang-bugs] error in rem operator Message-ID: I think I may have found a bug. Here's my factorial function: ///// -module(fact). -export([fact/1]). fact(N) -> fact(N,1). fact(0,P) -> P; fact(N,P) -> fact(N-1,P*N). ///// Now from the shell I did this: c(fact). X = fact:fact(1000). X rem 823543. %7^7=823543 This incorrectly gives 823543 instead of 0. Thanks! -----Jay From raimo+erlang-bugs@REDACTED Thu May 10 09:41:36 2007 From: raimo+erlang-bugs@REDACTED (Raimo Niskanen) Date: Thu, 10 May 2007 09:41:36 +0200 Subject: [erlang-bugs] error in rem operator In-Reply-To: References: Message-ID: <20070510074136.GA49@erix.ericsson.se> My modular math is a bit rusty, but is it not true that fact(X) rem 823543 == 0 for all X >= 49, since in the product fact(49) there are seven 7's making it divisible with 7 ^ 7 == 823543, and for any X > 49 it still must be divisible with 823543? I then find that for these X'es in the range [49..1000] rem 823543 /= 0 (according to Erlang): [50,51,85,89,90,93,95,96,131,132,133,134,135,136,137,140,141, 142,143,144,145,146,187,188,190,191,195,228,229,230,231,232, 234,235,237,238,239,244,277,278,280,282,283,284,285,286,287, 288,289,290,291,324,326,330,332,333,335,337,374,375,378,379, 380,383,385,420,421,422,425,426,429,432,433,436,437,470,473, 474,475,477,480,481,482,483,484,515,516,518,519,521,525,530, 531,564,566,569,570,573,575,576,578,579,612,613,615,618,621, 624,625,626,628,660,662,667,669,670,671,672,673,674,709,710, 713,717,718,719,722,723,760,761,762,763,770,805,808,810,814, 816,817,818,819,820,854,855,856,857,858,859,860,863,864,865, 867,868,869,900,902,904,905,908,910,911,912,914,916,917,952, 953,954,955,956,958,962,964,965,1000] So the problem starts at fact(50). 1> G = fun (G_, 0) -> 1; (G_, N) -> N * G_(G_, N-1) end. 2> G(G, 0). 3> G(G, 6). 4> L = [{N,G(G, N) rem 823543} || N <- lists:seq(49, 1000)]. [{49,0}, {50,823543}, {51,823543}, {52,0}, {53,0}, {54,0}, {55,0}, {56,0}, {57,0}, {58,0}, {59,0}, {60,0}, {61,0}, {62,0}, {63,0}, {64,0}, {65,0}, {66,0}, {67,0}, {68,0}, {69,0}, {70,0}, {71,0}, {72,0}, {73,0}, {74,0}, {75,0}, {76,...}, {...}|...] 5> erlang:display([N||{N,R} <- L, R =/= 0]). [50,51,85,89,90,93,95,96,131,132,133,134,135,136,137,140,141, 142,143,144,145,146,187,188,190,191,195,228,229,230,231,232, 234,235,237,238,239,244,277,278,280,282,283,284,285,286,287, 288,289,290,291,324,326,330,332,333,335,337,374,375,378,379, 380,383,385,420,421,422,425,426,429,432,433,436,437,470,473, 474,475,477,480,481,482,483,484,515,516,518,519,521,525,530, 531,564,566,569,570,573,575,576,578,579,612,613,615,618,621, 624,625,626,628,660,662,667,669,670,671,672,673,674,709,710, 713,717,718,719,722,723,760,761,762,763,770,805,808,810,814, 816,817,818,819,820,854,855,856,857,858,859,860,863,864,865, 867,868,869,900,902,904,905,908,910,911,912,914,916,917,952, 953,954,955,956,958,962,964,965,1000] true The question is then: is it a bug in rem or in the bignums? As you see I used another implementation of fact/1. On Thu, May 10, 2007 at 04:04:17AM +0000, Jay Anderson wrote: > I think I may have found a bug. Here's my factorial function: > > ///// > -module(fact). > -export([fact/1]). > > fact(N) -> fact(N,1). > fact(0,P) -> P; > fact(N,P) -> fact(N-1,P*N). > ///// > > Now from the shell I did this: > > c(fact). > X = fact:fact(1000). > X rem 823543. %7^7=823543 > > This incorrectly gives 823543 instead of 0. Thanks! > > -----Jay > > _______________________________________________ > erlang-bugs mailing list > erlang-bugs@REDACTED > http://www.erlang.org/mailman/listinfo/erlang-bugs -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From luna@REDACTED Thu May 10 09:44:45 2007 From: luna@REDACTED (Daniel Luna) Date: Thu, 10 May 2007 09:44:45 +0200 (CEST) Subject: [erlang-bugs] error in rem operator In-Reply-To: References: Message-ID: On Thu, 10 May 2007, Jay Anderson wrote: > I think I may have found a bug. Here's my factorial function: > > ///// > -module(fact). > -export([fact/1]). > > fact(N) -> fact(N,1). > fact(0,P) -> P; > fact(N,P) -> fact(N-1,P*N). > ///// > > Now from the shell I did this: > > c(fact). > X = fact:fact(1000). > X rem 823543. %7^7=823543 > > This incorrectly gives 823543 instead of 0. Thanks! There is something very strange going on here. Look at the result of: X div 823543. 48860503.....9999999999999 823543 is a factor of X, so X is evenly divisible by 823543. That means that the rest of the prime factors in X should still be there. I am missing a whole lot of 0s. (Tested on R11B-2) /Luna -- Daniel Luna | Top reasons that I have a beard: luna@REDACTED | a) Laziness. http://www.update.uu.se/~luna/ | b) I can. Don't look at my homepage (it stinks).| c) I can get away with it. From raimo+erlang-bugs@REDACTED Thu May 10 10:10:00 2007 From: raimo+erlang-bugs@REDACTED (Raimo Niskanen) Date: Thu, 10 May 2007 10:10:00 +0200 Subject: [erlang-bugs] : error in rem operator In-Reply-To: References: Message-ID: <20070510081000.GB49@erix.ericsson.se> Thank you guys! The bug is recognized. We will invesigate it. On Thu, May 10, 2007 at 09:44:45AM +0200, Daniel Luna wrote: > On Thu, 10 May 2007, Jay Anderson wrote: > > I think I may have found a bug. Here's my factorial function: > > > > ///// > > -module(fact). > > -export([fact/1]). > > > > fact(N) -> fact(N,1). > > fact(0,P) -> P; > > fact(N,P) -> fact(N-1,P*N). > > ///// > > > > Now from the shell I did this: > > > > c(fact). > > X = fact:fact(1000). > > X rem 823543. %7^7=823543 > > > > This incorrectly gives 823543 instead of 0. Thanks! > > There is something very strange going on here. > > Look at the result of: > > X div 823543. > > 48860503.....9999999999999 > > 823543 is a factor of X, so X is evenly divisible by 823543. That means > that the rest of the prime factors in X should still be there. I am > missing a whole lot of 0s. > > (Tested on R11B-2) > > /Luna > -- > Daniel Luna | Top reasons that I have a beard: > luna@REDACTED | a) Laziness. > http://www.update.uu.se/~luna/ | b) I can. > Don't look at my homepage (it stinks).| c) I can get away with it. > _______________________________________________ > erlang-bugs mailing list > erlang-bugs@REDACTED > http://www.erlang.org/mailman/listinfo/erlang-bugs -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From horndude77@REDACTED Fri May 11 03:40:27 2007 From: horndude77@REDACTED (Jay Anderson) Date: Fri, 11 May 2007 01:40:27 +0000 (UTC) Subject: [erlang-bugs] : error in rem operator References: <20070510081000.GB49@erix.ericsson.se> Message-ID: Raimo Niskanen erix.ericsson.se> writes: > > Thank you guys! > > The bug is recognized. We will invesigate it. > I'm glad I could help. Sorry I forgot to get you a version. What's the easiest way to do this and which version is most useful? (I'm new to erlang) I see "Erlang (BEAM) emulator version 5.5.2" when I start the shell. I installed the default package with ubuntu which as far as I can tell is R11b-2. What's the best way for finding this version. I couldn't find a command line switch which would give me a version. Thanks again for the help! -----Jay From matthias@REDACTED Fri May 11 08:24:30 2007 From: matthias@REDACTED (Matthias Lang) Date: Fri, 11 May 2007 08:24:30 +0200 Subject: [erlang-bugs] : error in rem operator In-Reply-To: References: <20070510081000.GB49@erix.ericsson.se> Message-ID: <17988.3102.892063.643136@antilipe.corelatus.se> Jay Anderson writes: > I'm glad I could help. Sorry I forgot to get you a version. > What's the easiest way to do this and which version is most useful? > (I'm new to erlang) I see "Erlang (BEAM) emulator version 5.5.2" > when I start the shell. That's probably enough. Another way is 1> init:script_id(). {"OTP APN 181 01","R11B"} this doesn't tell you the patchlevel, though. Matthias From hpjcon@REDACTED Fri May 18 06:50:43 2007 From: hpjcon@REDACTED (Jan Jacobs) Date: Fri, 18 May 2007 06:50:43 +0200 Subject: [erlang-bugs] odbcserver.exe and Windows 2003? Message-ID: <002c01c79908$19b2ba00$c800a8c0@jan03> Hi All, The odbcserver.exe has two behaviours which cause problems when running the software on a Windows 2003 server: 1) Orphan process. 2) Access violation errors. I have the software installed on 20 servers with the following results: 1) 60% of the servers has oprhan odbcserver.exe process. ( Random, process remains even if runtime is stopped! ) 2) 10% gives me rapeated access voilation errors! ( Always the same two windows boxes ) Any suggestions would be appreciated. As I get more information I will update the post. Thanks Jan Jacobs -------------- next part -------------- An HTML attachment was scrubbed... URL: From rtvd@REDACTED Thu May 31 06:48:58 2007 From: rtvd@REDACTED (Denys Rtveliashvili) Date: Thu, 31 May 2007 08:48:58 +0400 Subject: [erlang-bugs] crashes when running two servers with the same name Message-ID: <465E53BA.1000209@mail.ru> Hi, I experience crashes whenever I run two "erl" processes with the same name. Originally I tried to start a named server and connect to it like this: on terminal 1> erl -name FOO on terminal 2> erl -remsh FOO The first process runs fine while another one shows this error: *** ERROR: Shell process terminated! (^G to start new job) *** Then I tried to run two erl processes with the same name: on terminal 1> erl -name FOO on terminal 2> erl -name FOO The first process runs fine and the second one crashes: Crash dump was written to: erl_crash.dump Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}}) This does not seem to be related to compilation options or HiPE support. I tried different combinations for both v.11.2.4 and v.11.2.3. The computer I use runs Gentoo Linux on Intel Core 2 Duo processor. Could you please let me know how can I troubleshoot this issue? Thank you, Denys Rtveliasvhili From matthias@REDACTED Thu May 31 10:10:04 2007 From: matthias@REDACTED (Matthias Lang) Date: Thu, 31 May 2007 10:10:04 +0200 Subject: [erlang-bugs] crashes when running two servers with the same name In-Reply-To: <465E53BA.1000209@mail.ru> References: <465E53BA.1000209@mail.ru> Message-ID: <18014.33500.818039.657979@antilipe.corelatus.se> Denys Rtveliashvili writes: > I experience crashes whenever I run two "erl" processes with the > same name. "Doctor, doctor, it hurts whenever I stick a pencil in my eye." "Well, don't do that then". You are not allowed to start two erlang nodes with the same name. The error message tells you this in a fairly obscure way. They key is this part of the error message: {error_logger,{{2007,5,31},{10,7,28}},"Protocol: ~p: register error: ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}}, Matthias From matthias@REDACTED Thu May 31 10:54:50 2007 From: matthias@REDACTED (Matthias Radestock) Date: Thu, 31 May 2007 09:54:50 +0100 Subject: [erlang-bugs] crashes when running two servers with the same name In-Reply-To: <18014.33500.818039.657979@antilipe.corelatus.se> References: <465E53BA.1000209@mail.ru> <18014.33500.818039.657979@antilipe.corelatus.se> Message-ID: <465E8D5A.9070008@sorted.org> Matthias Lang wrote: > You are not allowed to start two erlang nodes with the same name. The > error message tells you this in a fairly obscure way. They key is this > part of the error message: > > {error_logger,{{2007,5,31},{10,7,28}},"Protocol: ~p: register error: ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}}, As an aside, *why* is the error message so obscure? It looks a bit like a "raw" error_logger event. Is that because of some unfortunate startup sequencing, i.e. the network sub-system gets started before the error_logger has been properly initialised? Matthias From bjorn@REDACTED Thu May 31 13:46:02 2007 From: bjorn@REDACTED (Bjorn Gustavsson) Date: 31 May 2007 13:46:02 +0200 Subject: [erlang-bugs] crashes when running two servers with the same name In-Reply-To: <465E8D5A.9070008@sorted.org> References: <465E53BA.1000209@mail.ru> <18014.33500.818039.657979@antilipe.corelatus.se> <465E8D5A.9070008@sorted.org> Message-ID: Matthias Radestock writes: > As an aside, *why* is the error message so obscure? It looks a bit like > a "raw" error_logger event. Is that because of some unfortunate startup > sequencing, i.e. the network sub-system gets started before the > error_logger has been properly initialised? Correct. /Bjorn -- Bj?rn Gustavsson, Erlang/OTP, Ericsson AB From xpdoka@REDACTED Thu May 31 17:00:14 2007 From: xpdoka@REDACTED (Dominic Williams) Date: Thu, 31 May 2007 17:00:14 +0200 (CEST) Subject: [erlang-bugs] undefined __erl_errno in erl_interface ? Message-ID: <2296.217.128.75.198.1180623614.squirrel@www.geekisp.com> Hello, A port that compiled fine under R10B-10 is failing to link because liberl_interface_st.a has undefined references to __erl_errno (under Linux): gcc -o ../priv/i386-redhat-linux/mysql_port.out ../priv/i386-redhat-linux/mysql_port.o -L/usr/X11R6/lib -L/usr/lib -L/usr/lib/mysql -lmysqlclient -L/usr/local/R11B-4/lib/erlang/lib/erl_interface-3.5.5.3/lib -lerl_interface_st -lei_st /usr/local/R11B-4/lib/erlang/lib/erl_interface-3.5.5.3/lib/liberl_interface_st.a(erl_eterm.o)(.text+0x105b): In function `erl_copy_term': legacy/erl_eterm.c:776: undefined reference to `__erl_errno' /usr/local/R11B-4/lib/erlang/lib/erl_interface-3.5.5.3/lib/liberl_interface_st.a(erl_eterm.o)(.text+0x11f2): In function `erl_mk_var': legacy/erl_eterm.c:497: undefined reference to `__erl_errno' /usr/local/R11B-4/lib/erlang/lib/erl_interface-3.5.5.3/lib/liberl_interface_st.a(erl_eterm.o)(.text+0x1288): In function `__erl_mk_reference': legacy/erl_eterm.c:254: undefined reference to `__erl_errno' /usr/local/R11B-4/lib/erlang/lib/erl_interface-3.5.5.3/lib/liberl_interface_st.a(erl_eterm.o)(.text+0x13b7): In function `erl_mk_port': legacy/erl_eterm.c:223: undefined reference to `__erl_errno' /usr/local/R11B-4/lib/erlang/lib/erl_interface-3.5.5.3/lib/liberl_interface_st.a(erl_eterm.o)(.text+0x145d): In function `erl_mk_pid': legacy/erl_eterm.c:192: undefined reference to `__erl_errno' /usr/local/R11B-4/lib/erlang/lib/erl_interface-3.5.5.3/lib/liberl_interface_st.a(erl_eterm.o)(.text+0x14de):legacy/erl_eterm.c:127: more undefined references to `__erl_errno' follow collect2: ld returned 1 exit status Has the definition of __erl_errno accidentally been removed, or should I be doing something different to compile under R10B-10 and R11B-4 ? Best regards, Dominic Williams http://dominicwilliams.net ---- From rtvd@REDACTED Thu May 31 18:30:05 2007 From: rtvd@REDACTED (Denys Rtveliashvili) Date: Thu, 31 May 2007 20:30:05 +0400 Subject: [erlang-bugs] crashes when running two servers with the same name In-Reply-To: <18014.33500.818039.657979@antilipe.corelatus.se> References: <465E53BA.1000209@mail.ru> <18014.33500.818039.657979@antilipe.corelatus.se> Message-ID: <465EF80D.8090602@mail.ru> Hi Matthias, Is this error message supposed to be in erl_crash.dump? I do see it neither there nor on console. Thanks for the hint about two nodes with the same name anyway. Regards, Denys Rtveliashvili > Denys Rtveliashvili writes: > > > I experience crashes whenever I run two "erl" processes with the > > same name. > > "Doctor, doctor, it hurts whenever I stick a pencil in my eye." > > "Well, don't do that then". > > You are not allowed to start two erlang nodes with the same name. The > error message tells you this in a fairly obscure way. They key is this > part of the error message: > > {error_logger,{{2007,5,31},{10,7,28}},"Protocol: ~p: register error: ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}}, > > Matthias > > >