You welcome, I made uat_load() idempotent to do exactly what you needed, It is used in oids.c to set the path and list the MIBS to be loaded, as such I needed it to be loaded at protocol registration and no later. To avoid it being loaded twice uat_load marks the uat as loaded.
\Lego On Fri, Apr 10, 2009 at 3:18 PM, Abhik Sarkar <sarkar.ab...@gmail.com> wrote: > Thank you, thank you, thank you, Luis! It never occurred to me that I could > load it manually. This worked! > > Also, it turns out that my original approach did not work because UAT > preferences is one of the only preference types which, if changed, doesn't > lead to the calling of the apply_cb passed in prefs_register_protocol... > Perhaps there is a reason for it, but for now, my requirement is met and I > am submitting a new patch. > > Thanks again! > Abhik. > > On Fri, Apr 10, 2009 at 8:06 AM, Luis EG Ontanon <l...@ontanon.org> wrote: >> >> You can call uat_load() to have it loaded before preferences. >> >> >> >> 2009/3/25 Abhik Sarkar <sarkar.ab...@gmail.com>: >> > Hi All, >> > >> > I want to read some data from a UAT while I am still in the registration >> > functions. Going through the documentation and the code, it seems that >> > all >> > UAT tables are loaded when preferences are being read, and that if some >> > registration needs to be done after preferences have been loaded, then >> > it >> > should be from inside proto_reg_handoff_protoname. My questions are: >> > - is my understanding correct? >> > - if not, is what I am trying to do possible at all? >> > I am trying to revise the patch which I submitted originally for >> > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3242 >> > >> > Thanks, >> > Abhik. >> > >> > >> > ___________________________________________________________________________ >> > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> > Archives: http://www.wireshark.org/lists/wireshark-dev >> > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> > >> > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe >> > >> >> >> >> -- >> This information is top security. When you have read it, destroy yourself. >> -- Marshall McLuhan >> >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> Archives: http://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe