Erlang Forum - Trap Exit

Erlang bugs mailing list :: cheap replica handbags

Author: wuji
Subject: cheap replica handbags
Posted: Tue Sep 11, 2012 3:37 am (GMT 0)
Topic Replies: 0

as planned since his visa was going to expire."That's their their replica designer handbags their choice, you know?" Arrechada said of his co-stars, according
the Huffington Post. "That's their way of thinking. No one one buy real jordans one is forced to stay. And no one is forced
go back. If you want to stay in the United United [h4]cheap authentic air jordans[/h4] United States, I think, well, stay. If you want to
back, go back. Not all of us have to stay stay cheap designer handbags stay and not all of us have to go back.
about what you want to do with your life."He told told real jordans told the website he believed his co-stars would stay in
U.S.A similar situation occurred in March when Yosmel de Armas, Armas, replica designer handbags Armas, a Cuban soccer player, defected from his national team
in Tennessee for a game. Armas turned up in Miami Miami imitation designer handbags Miami earlier this month and is seeking asylum with the
of an immigration attorney. John Edwards Trial: 'Truth May Be Be authentic jordans Be a Sin ... Not a Crime'Edwards Is Accused of
Using Campaign Funds to Hide an AffairBy BEN FORERApril 23, 23, cheap designer handbags 23, 2012 Today, during the opening statements of his trial

Erlang bugs mailing list :: cheap replica handbags

Author: wuji
Subject: cheap replica handbags
Posted: Thu Sep 06, 2012 8:43 am (GMT 0)
Topic Replies: 0

r homepage.Faking homepage.Faking authentic jordans homepage.Faking Heroism: Top Court to Rule on Stolen ValorSupreme Court
Decide Whether Freedom of Speech Protects Military Fakers With Phony Phony cheap real jordans Phony MedalsBy LEE FERRANJune 25, 2012 — In the few
left in its current term, the nation's highest court is is cheap replica designer handbags is set to decide a controversial case over whether people
lie about military honors should be protected under the First First [h4]imitation designer handbags[/h4] First Amendment's freedom of speech clause.California man Xavier Alvarez is
a law known as the Stolen Valor Act -- federal federal replica designer handbags federal legislation that in 2006 made it illegal for people
claim to have won or to wear military medals or or knockoff designer handbags or ribbons they did not earn. Alvarez was convicted of
the act in 2007 after he publicly claimed to have have [h1]cheap authentic jordans[/h1] have won the country's highest military award, the Medal of
Alvarez never served in the military.WATCH: Supreme Court Looks at at [h4]cheap replica designer handbags[/h4] at Stolen Valor ActAlvarez was sentenced to three years probation,
$5,000 fine and community service, but he and his lawyer lawyer replica designer handbags lawyer appealed the decision, saying that the Stolen Valor Act
unconstitutional -- essentially that it violates a person's right to to [h2]designer replica handbags[/h2] to lie."The Stolen Valor Act criminalizes pure speech in the

Erlang bugs mailing list :: confirm 11836d22427d49542e8fd43eb4d070b2a078da1d

Author: Anonymous
Subject: confirm 11836d22427d49542e8fd43eb4d070b2a078da1d
Posted: Wed Aug 24, 2011 8:52 am (GMT 0)
Topic Replies: 0

Your membership in the mailing list erlang-bugs has been disabled due
to excessive bounces The last bounce received from you was dated
06-Aug-2011. You will not get any more messages from this list until
you re-enable your membership. You will receive 1 more reminders like
this before your membership in the list is deleted.

To re-enable your membership, you can simply respond to this message
(leaving the Subject: line intact), or visit the confirmation page at

http://erlang.org/mailman/confirm/erlang-bugs/11836d22427d49542e8fd43eb4d070b2a078da1d

You can also visit your membership page at

http://erlang.org/mailman/options/erlang-bugs/trapexit.erlang-bugs%40erlang-solutions.com

On your membership page, you can change various delivery options such
as your email address and whether you get digests or not. As a
reminder, your membership password is

0r38nwht

If you have any questions or problems, you can contact the list owner
at

erlang-bugs-owner@erlang.org
Post received from mailinglist

Erlang bugs mailing list :: Dialyzer 2.3.0 crash on bitstring spec

Author: senderista
Subject: Dialyzer 2.3.0 crash on bitstring spec
Posted: Fri Feb 11, 2011 5:26 pm (GMT 0)
Topic Replies: 0

Hi, I tried running Dialyzer on a TypEr-generated typespec (for a function taking a bitstring param), and it crashes with case_clause error. Here is the test code and the dialyzer output:

Code:

-module(test).
-spec test_func(<<_:_*1>>) -> 'true'.
test_func(BitString) ->
true.

[~]$ dialyzer --verbose /Users/tobinba/test.erl
Checking whether the PLT /Users/tobinba/.dialyzer_plt is up-to-date... yes
Proceeding with analysis...
=ERROR REPORT==== 11-Feb-2011::09:13:56 ===
Error in process <0.29.0> with exit value: {{case_clause,1},[{erl_types,t_form_to_string,1},{erl_types,t_form_to_string,1},{dialyzer_contracts,contract_to_string_1,1},{dialyzer_contracts,extra_contract_warning,6},{dialyzer_contracts,picky_contract_check...

dialyzer: Analysis failed with error: {{case_clause,1},
[{erl_types,t_form_to_string,1},
{erl_types,t_form_to_string,1},
{dialyzer_contracts,contract_to_string_1,1},
{dialyzer_contracts,extra_contract_warning,6},
{dialyzer_contracts,picky_contract_check,7},
{dialyzer_contracts,get_invalid_contract_warnings_funs,4},
{dialyzer_contracts,get_invalid_contract_warnings_modules,...},
{dialyzer_succ_typings,...}]}
Last messages in the log cache:
Reading files and computing callgraph... done in 0.09 secs
Removing edges... done in 0.00 secs
Typesig analysis for SCC: [{test,module_info,1}]
Typesig analysis for SCC: [{test,test_func,1}]
Typesig analysis for SCC: [{test,module_info,0}]
Dataflow of one SCC: [test]

Erlang bugs mailing list :: xmerl_sax_parser:stream/2 doesn't know when to stop

Author: Anonymous
Subject: xmerl_sax_parser:stream/2 doesn't know when to stop
Posted: Fri Nov 12, 2010 12:23 pm (GMT 0)
Topic Replies: 1

Hi,
the problem you have encountered has nothing to do with the patch
http://www.erlang.org/cgi-bin/ezmlm-cgi/4/46754 .

The effect is also expected and I shall try to explain why.

According to the XML a document is defined as:

document ::= prolog element Misc*
Misc ::= Comment | PI | S

In the case you just give a string/binary to xmerl_sax_parser:stream/2 without a continuation function
to the parser it assumes that this is all input it will get and therefor it ends parsing (there is no default
continuation function).

But if you have defined a continuation function it will be called after the starting string/binary is parsed to see if
there is more and in your case the problem is that your function doesn't give anything that stops input.
io:getline gives at least a newline even if you just hit enter which is legal input at the end of the xml document.
As far as the parser knows it could come 10 newline and then a process instruction in the end.

When you type an x before hitting enter you got something that's not allowed at the end of the document.
The parser then returns that it got the end of a correct document and a rest value. If you have an input that consists
just of one document the rest should be [] (or <<>> depending on input). This function is parsing a stream and the rest
can be the start of a new document on the stream. The rest can then be used as a start of a new call
to xmerl_sax_parser:stream/2.

If you just want to read one document from input the continuation function must return a [] or <<>> (depending on the
input) to end the document.

Ex:
ContFun = fun(S) -> case io:get_line(">> ") of "\n" -> {"",S} ; X -> {X,S} end end.

Regards Lars Thorsen
OTP Team

Per Melin wrote:
> (I've only tested with R13B04 but there is nothing in the release
> notes that indicates that this would be different in R14B.)
>
> Without the continuation_fun option xmerl_sax_parser:stream/2 works as
> I would expect. But with a continuation_fun it needs to be fed at
> least one extra character after a complete document.
>
> 1> EventFun = fun(E, _, S) -> erlang:display(E), S end.
> #Fun<erl_eval.18.105910772>
> 2> ContFun = fun(S) -> {io:get_line(">> "), S} end.
> #Fun<erl_eval.6.13229925>
> 3> xmerl_sax_parser:stream("<foo />", [{event_fun, EventFun},
> {continuation_fun, ContFun}]).
> startDocument
> {startElement,[],"foo",{[],"foo"},[]}
> {endElement,[],"foo",{[],"foo"}}
>
> Here it has called ContFun and is waiting for additional input. It
> will accept anything that is not whitespace, and then return it as a
> rest. Let's give it an "x".
>
>>> x
> endDocument
> {ok,undefined,"x\n"}
> 4>
>
> It seems this used to be a problem even without continuation_fun, but
> the patch described here painted over it:
> http://www.erlang.org/cgi-bin/ezmlm-cgi/4/46754
>
> ________________________________________________________________
> erlang-bugs (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org
>

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist

Erlang bugs mailing list :: File naming

Author: Anonymous
Subject: File naming
Posted: Thu Nov 11, 2010 10:12 am (GMT 0)
Topic Replies: 4

Hello!

The run_test executable has been part of Erlang too long for it to be
renamed at this point without affecting a lot of projects. It has just
recently been moved into the default path of an installed Erlang system
which is probably why you haven't run into this issue before.

It is unfortunate that such a generic name was chosen (ct_run would have
been better imo) but alas there are too many people depending on that
name right now.

It is also strange that a voice synthesizer software has a exectutable
called run_test, but I guess they have the same reasons as we do for not
wanting to change that.

Lukas

On Mon, 2010-11-08 at 18:05 +0100, Christian Faulhammer wrote:
> Hi,
>
> the binary run_test is a badly chosen name as it is really generic and
> collides with a binary of the same name in the speech_dispatcher
> package. Is a rename to something more special like run_erlang_test
> possible without any sideeffects?
>
> V-Li
>

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist

Erlang bugs mailing list :: Crash in SSL-connection format_reply R13B04

Author: Anonymous
Subject: Crash in SSL-connection format_reply R13B04
Posted: Tue Nov 02, 2010 3:11 pm (GMT 0)
Topic Replies: 1

We get a crash in ssl_connection when trying to receive an http packet:

Here are some traces:

call ssl_connection:format_reply({socket_options,list,http,0,0,false},{http_request,'GET',{abs_path,"/"},{1,1}})
(<0.659.0>) call ssl_connection:format_reply(list,0,{http_request,'GET',{abs_path,"/"},{1,1}})
(<0.659.0>) exception_from {ssl_connection,format_reply,3} {error,badarg}
(<0.659.0>) exception_from {ssl_connection,format_reply,2} {error,badarg}
*failed*
::exit:{econnrefused,[{lhttpc_client,send_request,1},
{lhttpc_client,execute,9},
{lhttpc_client,request,9}]}
in function lhttpc:request/9
in call from tl_async:'-call/3-fun-0-'/3

(<0.659.0>) call ssl_connection:terminate({badarg,[{erlang,binary_to_list,[{http_request,'GET',{abs_path,"/"},{1,1}}]},
{ssl_connection,format_reply,3},
{ssl_connection,format_reply,2},
{ssl_connection,deliver_app_data,4},
{ssl_connection,application_data,2},
{ssl_connection,handle_event,3},

Relevant Code:
in ssl_connection.erl
format_reply(list, _, Data) -> binary_to_list(Data);
format_reply(binary, 0, Data) -> Data;
format_reply(binary, raw, Data) -> Data;
format_reply(binary, N, Data) -> % Header mode
<<Header:N/binary, Rest/binary>> = Data,
[binary_to_list(Header), Rest].

Is this already fixed in R14, and/or can we get a patch for R13B04 ?

Thanks

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist

Erlang bugs mailing list :: More void* arith errors

Author: Anonymous
Subject: More void* arith errors
Posted: Fri Oct 29, 2010 8:47 pm (GMT 0)
Topic Replies: 0

Same deal as before, SGI IRIX 6.5 + native sys compilers. Spat at a few more
cases where casting to char* is necessary for the build to continue.

cc-3316 c99: ERROR File = drivers/unix/unix_efile.c, Line = 1070
The expression must be a pointer to a complete object type.

w = write(fd, iov[cnt].iov_base + p, iov[cnt].iov_len -
p);
^

cc-3316 c99: ERROR File = drivers/unix/unix_efile.c, Line = 1076
The expression must be a pointer to a complete object type.

iov[cnt].iov_base += p;
^

cc-3316 c99: ERROR File = drivers/unix/unix_efile.c, Line = 1081
The expression must be a pointer to a complete object type.

iov[cnt].iov_base -= p;
^
===============================

cc-3316 c99: ERROR File = drivers/common/efile_drv.c, Line = 1157
The expression must be a pointer to a complete object type.

ev->iov[1 + c->cnt].iov_base + c->size,
^

cc-3316 c99: ERROR File = drivers/common/efile_drv.c, Line = 1433
The expression must be a pointer to a complete object type.

iov[iovcnt].iov_base + p,

cc-3316 c99: ERROR File = drivers/common/efile_drv.c, Line = 2965
The expression must be a pointer to a complete object type.

put_int32(n, res_ev->iov[0].iov_base+4);

Patrick Baggett

Post received from mailinglist

Erlang bugs mailing list :: Compile errors in beam/io.c on IRIX

Author: Anonymous
Subject: Compile errors in beam/io.c on IRIX
Posted: Fri Oct 29, 2010 12:50 pm (GMT 0)
Topic Replies: 2

Here's another problem I found when compiling beam/io.c for IRIX.
Since The OpenGroup defines the struct iovec::iov_base field to be a
void*, it is illegal to perform pointer arithmetic on it. I'm really
surprised this didn't show up in GCC or any other compiler.

Specifically, I get these errors.

cc-3316 c99: ERROR File = beam/io.c, Line = 3343
The expression must be a pointer to a complete object type.
iov->iov_base += skip;
^

cc-3316 c99: ERROR File = beam/io.c, Line = 3795
The expression must be a pointer to a complete object type.
iov->iov_base += skip;
^

cc-3316 c99: ERROR File = beam/io.c, Line = 3858
The expression must be a pointer to a complete object type.
iov->iov_base += skip;
^

cc-3316 c99: ERROR File = beam/io.c, Line = 3918
The expression must be a pointer to a complete object type.
q->v_head->iov_base += size;

-----
The implied goal here is to increment an address by a certain number
of bytes, so casting to a char* as follows will allow the compile to
succeed:

iov->iov_base = (char*)iov->iov_base + skip;

[I had sent a message a long time ago <sys/uio.h> not being
functional, but I was mistaken. Fortunately, it looks like nobody
implemented what I said, so there isn't anything to revert.]

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist

Erlang bugs mailing list :: ethread.h return in void function

Author: Anonymous
Subject: ethread.h return in void function
Posted: Fri Oct 29, 2010 11:09 am (GMT 0)
Topic Replies: 0

I started compiling Erlang R14B on IRIX 6.5 with the native system compilers
and it stopped on line 760 of ethread.h, which is trying to return a value
in a function that is declared to return void. Simple fix is to just remove
"return". It looks like a copy-paste error.

Any chance this could get patched for the next release? Obviously it isn't a
high priority since it is a one-liner fix for a platform without any native
atomic ops (yet).

Patrick Baggett

Post received from mailinglist

Erlang bugs mailing list :: bug in string:copies when copying float times character

Author: Anonymous
Subject: bug in string:copies when copying float times character
Posted: Fri Oct 29, 2010 7:07 am (GMT 0)
Topic Replies: 0

On Sun, Oct 24, 2010 at 01:02:36PM +0200, PAILLEAU Eric wrote:

> Number should obviously be an integer, but it seems there no
> guards on the type.
>
> I forgot do round my copy number of characters, I got crashes, and I
> finally found the problem :
>
> by doing :
> --------------------------------------------------------------------
> Erlang R14A (erts-5. [source] [smp:2:2] [rq:2] [async-threads:0]
> [hipe] [kernel-poll:false]
>
> Eshell V5.8 (abort with ^G)
> 1> string:copies("a",2.5).
>
> Crash dump was written to: erl_crash.dump
> eheap_alloc: Cannot allocate 1140328500 bytes of memory (of type "heap").
> --------------------------------------------------------------------

string:copies/2 decrements to 0 with each copy. With a float, 0 will
never be matched and the function goes into an infinite loop.

Using your suggestion of a guard fixes it:

1> string:copies("a",2.5).
** exception error: no function clause matching string:copies("a",2.5)

I'll send a patch to erlang-patches.

diff --git a/lib/stdlib/src/string.erl b/lib/stdlib/src/string.erl
index 6636a03..c987c22 100644
--- a/lib/stdlib/src/string.erl
+++ b/lib/stdlib/src/string.erl
@@ -202,5 +202,5 @@ chars(C, 0, Tail) when is_integer(C) ->
-spec copies(string(), non_neg_integer()) -> string().

-copies(CharList, Num) when is_list(CharList), Num >= 0 ->
+copies(CharList, Num) when is_list(CharList), is_integer(Num), Num >= 0 ->
copies(CharList, Num, []).

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist

Erlang bugs mailing list :: ODBC and net.ipv6.bindv6only

Author: Anonymous
Subject: ODBC and net.ipv6.bindv6only
Posted: Fri Oct 29, 2010 6:42 am (GMT 0)
Topic Replies: 2

Hi again!

After loking into this bug more closely I've found that the disabled
code (only for UNIX) does the following: it resolves "localhost" for
all available IP-addresses (IPv4 and IPv6) and tries to connect to all
of them sequentially (to the first success).

The problem is that localhost may have only IPv4 IP-address associated
with. In this case enabling IPv6 code will not fix the bug (though a
local admin will be able to fix it himself by adding ::1 localhost to
/etc/hosts).

So, I'm suggesting the following:

1) prefer IPv4 in odbc:init/1 instead of IPv6. This makes sure that in
all current environments ODBC will work (I'm not aware of anyone who
has IPv4 disabled other that for testing).

2) enable IPv6 capable code in odbcserver.c, which will make things
working if IPv6 is the only protocol (in this case it's very likely
that localhost resolves into ::1 and doesn't require special
attention).

I'm attaching a simple patch which does the above changes.

On Mon, Oct 18, 2010 at 12:27 PM, Ingela Anderton Andin
<ingela@erix.ericsson.se> wrote:
> Hi!
>
> I think it should be fairly safe to enable it, I am sure we had a good
> reason
> for doing this once upon a time but

Erlang bugs mailing list :: bug in string:copies when copying float times character

Author: Anonymous
Subject: bug in string:copies when copying float times character
Posted: Fri Oct 29, 2010 6:42 am (GMT 0)
Topic Replies: 0

Hello,
I found something weird, that can be considered as a bug.
Here is below the documentation for string:copies function.

---------------------------------------
copies(String, Number) -> Copies

Types:
String = Copies = string()
Number = integer()
---------------------------------------

Number should obviously be an integer, but it seems there no
guards on the type.

I forgot do round my copy number of characters, I got crashes, and I
finally found the problem :

by doing :
--------------------------------------------------------------------
Erlang R14A (erts-5. [source] [smp:2:2] [rq:2] [async-threads:0]
[hipe] [kernel-poll:false]

Eshell V5.8 (abort with ^G)
1> string:copies("a",2.5).

Crash dump was written to: erl_crash.dump
eheap_alloc: Cannot allocate 1140328500 bytes of memory (of type "heap").
--------------------------------------------------------------------

Erlang try to allocate the whole memory when trying to copy any float
number of characters. My computer is frozen a while, and reach hopefully
to garbage .

I got same behaviour in R13 and I did update to R14 in order to see if a
fix was done.

I guess an en exception 'badarith' or something else should be raised if
integer is not used on such function.

Best regards.

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist

Erlang bugs mailing list :: escript empty arguments on windows

Author: Anonymous
Subject: escript empty arguments on windows
Posted: Fri Oct 29, 2010 6:37 am (GMT 0)
Topic Replies: 0

There is a difference in the way escripts treats empty strings in the
argument list on Windows and Unix. Under cygwin and cmd any ""
parameters are stripped out and don't appear in the main(Args) list. The
Unix version of escript preserves these as an empty list. This looks
like a bug to me.

Regards

Emile

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist

Erlang bugs mailing list :: [erlang-patches] Fix SSL 4.0.1 handshake bug

Author: Anonymous
Subject: [erlang-patches] Fix SSL 4.0.1 handshake bug
Posted: Wed Aug 04, 2010 9:57 am (GMT 0)
Topic Replies: 0

On Wed, Aug 4, 2010 at 11:51 AM, Paul Guyot <pguyot@kallisys.net> wrote:
>
> git fetch git://github.com/pguyot/otp.git pg/fix-ssl-handshake-client-certificate
> http://github.com/pguyot/otp/commit/0975941a5b2684158ec8e94107a531f12827ca66

Thanks! Included in 'pu'.

--
Björn Gustavsson, Erlang/OTP, Ericsson AB

________________________________________________________________
erlang-bugs (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-bugs-unsubscribe@erlang.org

Post received from mailinglist