<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I am using R14B03, and apparently cannot
succeed in making good use of Dialyzer: I wanted first to generate a PLT
for the full Erlang/OTP install and then use it against my codebase to
perform more accurate checkings.</font>
<br>
<br><font size=2 face="sans-serif">So I generated a full PLT with a line
like:</font>
<br><font size=2 face="sans-serif">(this is slightly edited as actually
the building of the PLT is already integrated into the script we use to
streamline our Erlang installations)</font>
<br>
<br><font size=2 face="sans-serif">${prefix}/bin/dialyzer --build_plt -r
${prefix}/lib/erlang --output_plt ${prefix}/Erlang-R14B03.plt</font>
<br>
<br><font size=2 face="sans-serif">The operation seems to succeed and I
end up some time later with a 4.4MB PLT file.</font>
<br>
<br><font size=2 face="sans-serif">However if I run it against a random
module of us:</font>
<br>
<br><font size=2 face="sans-serif"> ${prefix}/bin/dialyzer --plt ${prefix}/Erlang-R14B03.plt
--output_plt ./common.plt src/utils/basic_utils.beam --build_plt</font>
<br>
<br><font size=2 face="sans-serif">It looks as if the previous PLT was
not used:</font>
<br>
<br><font size=2 face="sans-serif"> Creating PLT ./common.plt ...</font>
<br><font size=2 face="sans-serif">Unknown functions:</font>
<br><font size=2 face="sans-serif"> calendar:datetime_to_gregorian_seconds/1</font>
<br><font size=2 face="sans-serif"> calendar:seconds_to_daystime/1</font>
<br><font size=2 face="sans-serif"> code:get_object_code/1</font>
<br><font size=2 face="sans-serif"> global:register_name/2</font>
<br><font size=2 face="sans-serif"> global:unregister_name/1</font>
<br><font size=2 face="sans-serif"> global:whereis_name/1</font>
<br><font size=2 face="sans-serif"> os:cmd/1</font>
<br><font size=2 face="sans-serif"> random:seed/0</font>
<br><font size=2 face="sans-serif"> random:seed/3</font>
<br><font size=2 face="sans-serif"> random:uniform/0</font>
<br><font size=2 face="sans-serif"> random:uniform/1</font>
<br><font size=2 face="sans-serif"> rpc:multicall/5</font>
<br><font size=2 face="sans-serif"> sets:from_list/1</font>
<br><font size=2 face="sans-serif"> sets:to_list/1</font>
<br><font size=2 face="sans-serif"> string:tokens/2</font>
<br><font size=2 face="sans-serif"> text_utils:string_to_integer/1</font>
<br><font size=2 face="sans-serif"> timer:sleep/1</font>
<br><font size=2 face="sans-serif"> done in 0m0.58s</font>
<br><font size=2 face="sans-serif">done (passed successfully)</font>
<br>
<br><font size=2 face="sans-serif">Most of these functions come from stdlib
and al, so I would expect them to be in Erlang-R14B03.plt. </font>
<br><font size=2 face="sans-serif">And if I run, as an example (calendar
being among the missing modules):</font>
<br>
<br><font size=2 face="sans-serif">${prefix}/dialyzer --plt_info --plt
${prefix}/Erlang-R14B03.plt | grep calendar</font>
<br>
<br><font size=2 face="sans-serif">I have:</font>
<br><font size=2 face="sans-serif"> "${prefix}/lib/erlang/lib/stdlib-1.17.4/ebin/calendar.beam",</font>
<br>
<br><font size=2 face="sans-serif">So apparently the two calendar functions
should be known of this PLT.</font>
<br>
<br><font size=2 face="sans-serif">I must be making some mistake, but I
tried different other approaches (ex: with '--apps erts kernel stdlib'
instead of a wide '-r ') but with no luck.</font>
<br>
<br><font size=2 face="sans-serif">Are the installed BEAMs stripped in
some way of debug_info/type specs, or anything like that ?</font>
<br>
<br><font size=2 face="sans-serif">Any help appreciated!</font>
<br>
<br><font size=2 face="sans-serif">Thanks in advance,</font>
<br><font size=2 face="sans-serif">Best regards,</font>
<br>
<br><font size=2 face="sans-serif">Olivier.<br>
---------------------------<br>
Olivier Boudeville<br>
<br>
EDF R&D : 1, avenue du Général de Gaulle, 92140 Clamart, France<br>
Département SINETICS, groupe ASICS (I2A), bureau B-226<br>
Office : +33 1 47 65 59 58 / Mobile : +33 6 16 83 37 22 / Fax : +33 1 47
65 27 13</font><font face="monospace"><br>
<br>
<br>
Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.<br>
<br>
Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.<br>
<br>
Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.<br>
____________________________________________________<br>
<br>
This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.<br>
<br>
If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.<br>
<br>
E-mail communication cannot be guaranteed to be timely secure, error or virus-free.</font>