That's exactly the case. I am submitting a patch to otp/dialyzer to add an
option to not error out on issues like these.

And I was formatting that error with ~p, but for some reason it wasn't smart
enough to know the whole error was a string. Not sure why..

Thanks!
JW

On Sat, Mar 26, 2011 at 7:23 PM, Martin Logan <martinjlo...@gmail.com>wrote:

> My guess would be that getopt was compiled with make and published and
> that is why it does not have debug info. Pull it, sinan compile it
> with debug info, and then publish
>
> On Sat, Mar 26, 2011 at 6:22 PM, Martin Logan <martinjlo...@gmail.com>
> wrote:
> > whoops, haha, that was my fault. Here is your error message fo real dis
> time:
> >
> > Could not get abstract code for file:
> > "/usr/local/lib/erlang/lib/getopt-0.3.0/ebin/getopt.beam" (please
> > recompile it with +debug_info)
> >
> > On Sat, Mar 26, 2011 at 6:18 PM, Martin Logan <martinjlo...@gmail.com>
> wrote:
> >> One way is to take all the numbers and run them through a io:format as
> such
> >>
> >> 1> io:format("~p~n",
> >> [[67,111,117,108,100,32,110,111,116,32,103,101,116,32,97,98,
> >> 1> >
> 115,116,114,97,99,116,32,99,111,100,101,32,102,111,114,32,
> >> 1> >                  102,105,108,101,58,32]]).
> >> * 2: syntax error before: '>'
> >>
> >>
> >> so you have some kind of syntax error near a '>' print the others and
> >> see what you get
> >>
> >> On Sat, Mar 26, 2011 at 10:02 AM, Jordan Wilberding
> >> <jwilberd...@gmail.com> wrote:
> >>> Anyone know how to get a more understandable error out of this?
> >>> 17>
> >>>
> dialyzer:run([{files_rec,["/usr/local/lib/erlang/lib/getopt-0.3.0/ebin"]},{from,byte_code},{analysis_type,plt_build},{output_plt,"/home/diginux/code/sinan/_build/development/info/dialyzer_plt"}]).
> >>> ** exception throw:
> >>> {dialyzer_error,[67,111,117,108,100,32,110,111,116,32,103,
> >>>
> >>> 101,116,32,97,98,115,116,114,97,99,116,32,99,111,100,101|...]}
> >>>      in function  dialyzer_plt:compute_md5_from_file/1
> >>>      in call from dialyzer_plt:'-compute_md5_from_files/1-lc$^0/1-0-'/1
> >>>      in call from dialyzer_plt:compute_md5_from_files/1
> >>>      in call from dialyzer_cl:build_plt/1
> >>>      in call from dialyzer:run/1
> >>> 18> try
> >>>
> dialyzer:run([{files_rec,["/usr/local/lib/erlang/lib/getopt-0.3.0/ebin"]},{from,byte_code},{analysis_type,plt_build},{output_plt,"/home/diginux/code/sinan/_build/development/info/dialyzer_plt"}])
> >>> catch Blah -> io:format("~p~n",[Blah]) end.
> >>>
> {dialyzer_error,[67,111,117,108,100,32,110,111,116,32,103,101,116,32,97,98,
> >>>
> 115,116,114,97,99,116,32,99,111,100,101,32,102,111,114,32,
> >>>                  102,105,108,101,58,32,
> >>>
> >>> "/usr/local/lib/erlang/lib/getopt-0.3.0/ebin/getopt.beam",32,
> >>>
> >>> 40,112,108,101,97,115,101,32,114,101,99,111,109,112,105,108,
> >>>
> 101,32,105,116,32,119,105,116,104,32,43,100,101,98,117,103,
> >>>                  95,105,110,102,111,41,10]}
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "erlware-dev" group.
> >>> To post to this group, send email to erlware-dev@googlegroups.com.
> >>> To unsubscribe from this group, send email to
> >>> erlware-dev+unsubscr...@googlegroups.com.
> >>> For more options, visit this group at
> >>> http://groups.google.com/group/erlware-dev?hl=en.
> >>>
> >>
> >>
> >>
> >> --
> >> Martin Logan
> >> Erlang & OTP in Action (Manning) http://manning.com/logan
> >> http://twitter.com/martinjlogan
> >> http://erlware.org
> >>
> >
> >
> >
> > --
> > Martin Logan
> > Erlang & OTP in Action (Manning) http://manning.com/logan
> > http://twitter.com/martinjlogan
> > http://erlware.org
> >
>
>
>
> --
> Martin Logan
> Erlang & OTP in Action (Manning) http://manning.com/logan
> http://twitter.com/martinjlogan
> http://erlware.org
>

-- 
You received this message because you are subscribed to the Google Groups 
"erlware-dev" group.
To post to this group, send email to erlware-dev@googlegroups.com.
To unsubscribe from this group, send email to 
erlware-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/erlware-dev?hl=en.

Reply via email to