[Bro-Dev] [JIRA] (BIT-1192) record initialization weirdness

Jon Siwek (JIRA) jira at bro-tracker.atlassian.net
Mon May 19 12:06:07 PDT 2014


    [ https://bro-tracker.atlassian.net/browse/BIT-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602#comment-16602 ] 

Jon Siwek commented on BIT-1192:
--------------------------------

It's coercing the record in to a string (the type of the first field) where I would expect there might be some type check that could emit an error instead.  I'll see if it's an easy fix to do during beta.

> record initialization weirdness
> -------------------------------
>
>                 Key: BIT-1192
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1192
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: Bro
>    Affects Versions: git/master
>            Reporter: Justin Azoff
>            Priority: Low
>              Labels: language
>             Fix For: 2.3
>
>
> If you redundantly define a record as in cmd_bad:
> {code}
> event bro_init()
> {
>     local strcmd = "echo hi";
>     print "inline", [$cmd=strcmd];
>     local cmd_ok = Exec::Command($cmd=strcmd);
>     print "ok", cmd_ok;
>     local cmd_bad = Exec::Command([$cmd=strcmd]);
>     print "bad", cmd_bad;
> }
> {code}
> You get this:
> {code}
> inline, [cmd=echo hi]
> ok, [cmd=echo hi, stdin=, read_files=<uninitialized>, uid=BHMrHdIapni]
> bad, [cmd=[cmd=echo hi], stdin=, read_files=<uninitialized>, uid=NsfjD555BY1]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3-OD-04-019#6322)


More information about the bro-dev mailing list