+ i. Rt^RIHt^RIHt]'gR]9d^RIH t M^RI t ^RI t Rt RtRtR t!R R ]4t^RIt] P(t^R IHtHtHt^RIt] P4t] P6t] P8t] P:t] P<t] P>t] P@t ] PBt!] PDt"] PFt#] PHt$] PJt%] PLt&] PNt'] PPt(] PRt)] PTt*] PVt+] PXt,] PZt-] P\t.] P^t/] P`t0] Pbt1] Pdt2] Pft3] Pht4] Pjt5] Plt6] Pnt7] Ppt8] Prt9] Ptt:] Pvt;] Pxt<] Pzt=] P|t>] P~t?] Pt@] PtA] PtB] PtC] PtD] PtE] PtF] PtG] PtH] PtI] PtJ] PtK] PtL] PtM] PtN] PtO] PtP] PtQ] PtR] PtS] PtT] PtU] PtVR RltW!RR]X4tY] P!]Y4!RR]X4t[] P!][4!RR]X4t]] P!]]4] Pt_] Pt`] Pta] Ptb] Ptc] Ptd] Pte] Ptf] Ptg] Pth] Pti!RR]X4tj] P!]j4] Ptl] Ptm] Ptn] Pto] Ptp] Ptq] Ptr] Pts] Ptt] Ptu] Ptv] Ptw] Ptx!RR]X4ty] P!]y4!RR]X4t{] P!]{4R#RRllt}R$RRllt~RR ltR!R"ltR# ] d ^RI t ELei;i)%a/Merge functionality. NOTE: this functionality is available in IDA Teams (not IDA Pro) There are 3 databases involved in merging: base_idb, local_db, and remote_idb. * base_idb: the common base ancestor of 'local_db' and 'remote_db'. in the UI this database is located in the middle. * local_idb: local database that will contain the result of the merging. in the UI this database is located on the left. * remote_idb: remote database that will merge into local_idb. It may reside locally on the current computer, despite its name. in the UI this database is located on the right. base_idb and remote_idb are opened for reading only. base_idb may be absent, in this case a 2-way merging is performed. Conflicts can be resolved automatically or interactively. The automatic resolving scores the conflicting blocks and takes the better one. The interactive resolving displays the full rendered contents side by side, and expects the user to select the better side for each conflict. Since IDB files contain various kinds of information, there are many merging phases. The entire list can be found in merge.cpp. Below are just some selected examples: * merge global database settings (inf and other global vars) * merge segmentation and changes to the database bytes * merge various lists: exports, imports, loaded tils, etc * merge names, functions, function frames * merge debugger settings, breakpoints * merge struct/enum views * merge local type libraries * merge the disassembly items (i.e. the segment contents) this includes operand types, code/data separation, etc * merge plugin specific info like decompiler types, dwarf mappings, etc To unify UI elements of each merge phase, we use merger views: * A view that consists of 2 or 3 panes: left (local_idb) and right (remote_idb). The common base is in the middle, if present. * Rendering of the panes depends on the phase, different phases show different contents. * The conflicts are highlighted by a colored background. Also, the detail pane can be consulted for additional info. * The user can select a conflict (or a bunch of conflicts) and say "use this block". * The user can browse the panes as he wishes. He will not be forced to handle conflicts in any particular order. However, once he finishes working with a merge handler and proceeds to the next one, he cannot go back. * Scrolling the left pane will synchronously scroll the right pane and vice versa. * There are the navigation commands like "go to the prev/next conflict" * The number of remaining conflicts to resolve is printed in the "Progress" chooser. * The user may manually modify local database inside the merger view. For that he may use the regular hotkeys. However, editing the database may lead to new conflicts, so we better restrict the available actions to some reasonable minimum. Currently, this is not implemented. IDA works in a new "merge" mode during merging. In this mode most events are not generated. We forbid them to reduce the risk that a rogue third-party plugin that is not aware of the "merge" mode would spoil something. For example, normally renaming a function causes a cascade of events and may lead to other database modifications. Some of them may be desired, some - not. Since there are some undesired events, it is better to stop generating them. However, some events are required to render the disassembly listing. For example, ev_ana_insn, av_out_insn. This is why some events are still generated in the "merge" mode. To let processor modules and plugins merge their data, we introduce a new event: ev_create_merge_handlers. It is generated immediately after opening all three idbs. The interested modules should react to this event by creating new merge handlers, if they need them. While the kernel can create arbitrary merge handlers, modules can create only the standard ones returned by: create_nodeval_merge_handler() create_nodeval_merge_handlers() create_std_modmerge_handlers() We do not document merge_handler_t because once a merge handler is created, it is used exclusively by the kernel. See mergemod.hpp for more information about the merge mode for modules. ) annotations) version_info.) _ida_mergeNcRVPP4,pRVPP : RVPP : RV: R2# \PdRpLPi;i)z proxy of )this__repr__ __builtin__ Exception __class__ __module____name__)selfstrthiss& AC:\Users\user\Downloads\ida93sp2\portable_win\python\ida_merge.py _swig_reprr7sg 2 2 44"^^669   s!AA43A4caV3RlpV#)c<VR8Xd S!WV4R#VR8XdVPPV4R#\W4'd5\\ \ V4V4\ 4'd S!WV4R#\RV,4h)r thisownz(You cannot add instance attributes to %sN)r ownhasattr isinstancegetattrtypepropertyAttributeError)rnamevaluesets&&&rset_instance_attrE_swig_setattr_nondynamic_instance_variable..set_instance_attrBsu 6> E " Y  IIMM% T ZT D0I && E " !K" )r r!sf r*_swig_setattr_nondynamic_instance_variabler%@s  r#caV3RlpV#)c<\W4'd+\\W4\4'g S!WV4R#\ RV,4h)z%You cannot add class attributes to %sN)rrrrr)clsrrr s&&&rset_class_attr?_swig_setattr_nondynamic_class_variable..set_class_attrRs: 3  j1CX&N&N 5 ! !H3!NO Or#r$)r r)sf r'_swig_setattr_nondynamic_class_variabler+PsP r#caV3RlpV#)zlClass decorator for adding a metaclass to a SWIG wrapped class - a slimmed down version of six.add_metaclasscp<S!VPVPVPP44#N)r __bases____dict__copy)r( metaclasss&rwrapper$_swig_add_metaclass..wrapper]s's}}cll6G6G6IJJr#r$)r2r3sf r_swig_add_metaclassr5ZsK Nr#c>]tRt^btRt]!]P4tRtR#)_SwigNonDynamicMetazKMeta class to enforce nondynamic attributes (no new attributes) for a classr$N) rr __qualname____firstlineno____doc__r+r __setattr____static_attributes__r$r#rr7r7bsU9$:J:JKKr#r7)TupleListUnioncV^8dQhRR/#returnboolr$)formats"r __annotate__rF"s++4+r#c,\P!4#)zSReturn TRUE if IDA is running in diff mode (MERGE_POLICY_MDIFF/MERGE_POLICY_VDIFF) )ris_diff_merge_moder$r#rrHrH"s  ( ( **r#c.]tRtRt$]!RRRR7tRt]t]!] P] P4t R] R&]!] P] P4tR ] R &]!] P"] P$4tR ] R &]!] P(] P*4tR ] R&]!] P.] P04tR] R&RRltRRltRRltRRltRRltRRltRRlt RR lt!R!R"lt"R+R#R$llt#R+R%R&llt$R'R(lt%R)t&R*#), merge_data_ti(c 6VPP4#r.r rxs&rmerge_data_t.)r#c 8VPPV4#r.rLrNvs&&rrOrP)AFFJJqMr#The membership flagdocc \R4h)zNo constructor defined)r)rargskwargss&*,r__init__merge_data_t.__init__,s566r#z 'int [3]' dbctx_idsintnbasesz'merge_handlers_t' ev_handlersz&'merge_data_t::item_block_locator_t *'item_block_locator'merge_handler_t *'last_udt_related_mergerc(V^8dQhRRRRRRRR/#)rBlocalr_remotebaserCNoner$)rEs"rrFmerge_data_t.__annotate__Bs.PP3PP3P$Pr#c 0\P!WW#4#r.)rmerge_data_t_set_dbctx_ids)rrfrgrhs&&&&r set_dbctx_idsmerge_data_t.set_dbctx_idsBs44T&OOr#cV^8dQhRR/#rBrCr_r$)rEs"rrFrjEs666r#c .\P!V4#r.)rmerge_data_t_local_idrs&rlocal_idmerge_data_t.local_idEs//55r#cV^8dQhRR/#rpr$)rEs"rrFrjHs77#7r#c .\P!V4#r.)rmerge_data_t_remote_idrss&r remote_idmerge_data_t.remote_idHs0066r#cV^8dQhRR/#rpr$)rEs"rrFrjKs555r#c .\P!V4#r.)rmerge_data_t_base_idrss&rbase_idmerge_data_t.base_idKs..t44r#c V^8dQhRRRR/#rBhandlerrcrCrir$)rEs"rrFrjNsHH)<HHr#c .\P!W4#r.)rmerge_data_t_add_event_handlerrrs&&radd_event_handlermerge_data_t.add_event_handlerNs88GGr#c V^8dQhRRRR/#rr$)rEs"rrFrjQsKK,?K4Kr#c .\P!W4#r.)r!merge_data_t_remove_event_handlerrs&&rremove_event_handler!merge_data_t.remove_event_handlerQs;;DJJr#c$V^8dQhRRRRRR/#)rBidx'diff_source_idx_t' item_headida_idaapi.ea_trCr$)rEs"rrFrjTs)LL"5LL*Lr#c 0\P!WV4#r.)rmerge_data_t_get_block_head)rrrs&&&rget_block_headmerge_data_t.get_block_headTs55dKKr#c(V^8dQhRRRRRRRR/#)rBdst_idxrsrc_idxregion'diff_range_t const &'rCrDr$)rEs"rrFrjXs,$7%;?Cr#c 2\P!WVV4#r.)rmerge_data_t_setup_blocks)rrrrs&&&&r setup_blocksmerge_data_t.setup_blocksXs33D7  r#c V^8dQhRRRR/#)rBnodenamestrrCrDr$)rEs"rrFrj]sII#IIr#c .\P!W4#)z+check that node exists in any of databases )rmerge_data_t_has_existing_node)rrs&&rhas_existing_nodemerge_data_t.has_existing_node]s88HHr#c 0V^8dQhRRRRRRRRRR R R /#) rBtidz 'tid_t *'ear_fromrtostrictrDrCr$)rEs"rrFrjbs:  I ?  !4 >B   r#c 4\P!WVW4V4#)amap IDs of structures, enumerations and their members :param tid: item ID in TO database :param ea: item ID to find counterpart :param to: destination database index, diff_source_idx_t :param strict: raise interr if could not map :returns: success)rmerge_data_t_map_privrange_id)rrrrrrs&&&&&&rmap_privrange_idmerge_data_t.map_privrange_idbs 772 v r#c ,V^8dQhRRRRRRRRRR/#) rBtif 'tinfo_t'rrrrrDrCr$)rEs"rrFrjos:OOYO/BOO%)O26Or#c 2\P!WW#V4#)amigrate type, replaces type references into FROM database to references into TO database :param tif: type to migrate, will be cleared in case of fail :param to: destination database index, diff_source_idx_t :param strict: raise interr if could not map :returns: success)rmerge_data_t_map_tinfo)rrrrrs&&&&&r map_tinfomerge_data_t.map_tinfoos00EvNNr#c ,V^8dQhRRRRRRRRRR/#) rBtif1rdiffidx1rtif2diffidx2rCr_r$)rEs"rrFrjys3 & & & &#, &8K &  &r#c 2\P!WW#V4#)zcompare types from two databases :param tif1: type :param diffidx1: database index, diff_source_idx_t :param tif2: type :param diffidx2: database index, diff_source_idx_t :returns: -1, 0, 1)r!merge_data_t_compare_merging_tifs)rrrrrs&&&&&rcompare_merging_tifs!merge_data_t.compare_merging_tifsys;;D H& &r#r$NT)'rrr8r9rrr\rr rmerge_data_t_dbctx_ids_getmerge_data_t_dbctx_ids_setr^__annotations__merge_data_t_nbases_getmerge_data_t_nbases_setr`merge_data_t_ev_handlers_getmerge_data_t_ev_handlers_setra#merge_data_t_item_block_locator_get#merge_data_t_item_block_locator_setrb(merge_data_t_last_udt_related_merger_get(merge_data_t_last_udt_related_merger_setrdrmrtryr~rrrrrrrrr<r$r#rrJrJ(s&-/I !#G7H#J$I$I--/Iy/:==z!FC! &.z$$j&M&M'OK#OAI66 ++B->-4rQr#c 8VPPV4#r.rLrSs&&rrOrrUr#rVrWc(V^8dQhRRRRRRRR/#)rBmd'merge_data_t'rrrrrCr$)rEs"rrF!item_block_locator_t.__annotate__s+6I"&5r#c 2\P!WVV4#r.)r#item_block_locator_t_get_block_head)rrrrs&&&&rr#item_block_locator_t.get_block_heads==d  r#c ,V^8dQhRRRRRRRRRR /#) rBrrrrrrrrCrDr$)rEs"rrFrs3~6I )?CGr#c 2\P!WVW44#r.)r!item_block_locator_t_setup_blocks)rrrrrs&&&&&rr!item_block_locator_t.setup_blockss;;De  r#c VP\8XdRpMTp\P!V\P!V44R#r.)r rritem_block_locator_t_swiginitnew_item_block_locator_tr_selfs& rr\item_block_locator_t.__init__s> >>1 1EE00z $ $8%%*8, -r#c VPP4\P!V4\P !V4#r.)r disownrdisown_item_block_locator_tweakrefproxyrss&r __disown__item_block_locator_t.__disown__s/ ..t4}}T""r#r$N)rrr8r9rrrr rrrdelete_item_block_locator_t__swig_destroy__r\rr<r$r#rrrs<-/I !#GH "==-#r#rc]tRtRt$]!RRRR7t]t]!]P4t R] R&]!]P]P4tR] R &]!]P]P 4tR ] R &]!]P$]P&4tR ] R &]!]P*]P,4tR ] R&RRltRRltRRltRRltRRltRRltRRltRRltRR lt ]PBt"R!t#R"#)#merge_handler_params_tic 6VPP4#r.rLrMs&rrOmerge_handler_params_t.rQr#c 8VPPV4#r.rLrSs&&rrOrrUr#rVrWz'merge_data_t &'rrlabel'merge_kind_t'kind insert_afterr_mh_flagsc ,V^8dQhRRRRRRRRRR /#) rB_mdr_labelr_kindr _insert_after _mh_flagsr_r$)rEs"rrF#merge_handler_params_t.__annotate__s2NC'5BEr#c  `\P!V\P!WW4V44R#r.)rmerge_handler_params_t_swiginitnew_merge_handler_params_t)rrrrrrs&&&&&&rr\merge_handler_params_t.__init__s,224 & &:''*E : r#cV^8dQhRR/#rAr$)rEs"rrFrsMMdMr#c 2\P!V.VO5!#)zThis function has the following signatures: 0. ui_has_details() -> bool 1. ui_has_details(_mh_flags: int) -> bool # 0: ui_has_details() -> bool # 1: ui_has_details(_mh_flags: int) -> bool Should IDA display the diffpos detail pane? )r%merge_handler_params_t_ui_has_detailsrrZs&*rui_has_details%merge_handler_params_t.ui_has_detailss??LtLLr#cV^8dQhRR/#rAr$)rEs"rrFrs$r#c 2\P!V.VO5!#)aThis function has the following signatures: 0. ui_complex_details() -> bool 1. ui_complex_details(_mh_flags: int) -> bool # 0: ui_complex_details() -> bool # 1: ui_complex_details(_mh_flags: int) -> bool Do not display the diffpos details in the chooser. For example, the MERGE_KIND_SCRIPTS handler puts the script body as the diffpos detail. It would not be great to show them as part of the chooser. )r)merge_handler_params_t_ui_complex_detailsrs&*rui_complex_details)merge_handler_params_t.ui_complex_detailss CCD4 r#cV^8dQhRR/#rAr$)rEs"rrFrNNtNr#c 2\P!V.VO5!#)abThis function has the following signatures: 0. ui_complex_name() -> bool 1. ui_complex_name(_mh_flags: int) -> bool # 0: ui_complex_name() -> bool # 1: ui_complex_name(_mh_flags: int) -> bool It customary to create long diffpos names having many components that are separated by any 7-bit ASCII character (besides of '\0'). In this case it is possible to instruct IDA to use this separator to create a multi-column chooser. For example the MERGE_KIND_ENUMS handler has the following diffpos name: enum_1,enum_2 If MH_UI_COMMANAME is specified, IDA will create 2 columns for these names. )r&merge_handler_params_t_ui_complex_namers&*rui_complex_name&merge_handler_params_t.ui_complex_name@@MMMr#cV^8dQhRR/#)rBrCz'char'r$)rEs"rrFrs L LV Lr#c 2\P!V.VO5!#)zThis function has the following signatures: 0. ui_split_char() -> char 1. ui_split_char(_mh_flags: int) -> char # 0: ui_split_char() -> char # 1: ui_split_char(_mh_flags: int) -> char )r$merge_handler_params_t_ui_split_charrs&*r ui_split_char$merge_handler_params_t.ui_split_chars>>tKdKKr#cV^8dQhRR/#)rBrCrr$)rEs"rrFrs K KC Kr#c 2\P!V.VO5!#)zThis function has the following signatures: 0. ui_split_str() -> str 1. ui_split_str(_mh_flags: int) -> str # 0: ui_split_str() -> str # 1: ui_split_str(_mh_flags: int) -> str )r#merge_handler_params_t_ui_split_strrs&*r ui_split_str#merge_handler_params_t.ui_split_strs==dJTJJr#cV^8dQhRR/#rAr$)rEs"rrFrr r#c 2\P!V.VO5!#)aThis function has the following signatures: 0. ui_dp_shortname() -> bool 1. ui_dp_shortname(_mh_flags: int) -> bool # 0: ui_dp_shortname() -> bool # 1: ui_dp_shortname(_mh_flags: int) -> bool The detail pane shows the diffpos details for the current diffpos range as a tree-like view. In this pane the diffpos names are used as tree node names and the diffpos details as their children. Sometimes, for complex diffpos names, the first part of the name looks better than the entire name. For example, the MERGE_KIND_SEGMENTS handler has the following diffpos name: ,,, if MH_UI_DP_SHORTNAME is specified, IDA will use as a tree node name )r&merge_handler_params_t_ui_dp_shortnamers&*rui_dp_shortname&merge_handler_params_t.ui_dp_shortnamerr#cV^8dQhRR/#rAr$)rEs"rrFr"sJJ4Jr#c 2\P!V.VO5!#)aThis function has the following signatures: 0. ui_linediff() -> bool 1. ui_linediff(_mh_flags: int) -> bool # 0: ui_linediff() -> bool # 1: ui_linediff(_mh_flags: int) -> bool In detail pane IDA shows difference between diffpos details. IDA marks added or deleted detail by color. In the modified detail the changes are marked. Use this UI hint if you do not want to show the differences inside detail. )r"merge_handler_params_t_ui_linediffrs&*r ui_linediff"merge_handler_params_t.ui_linediff"s< bool 1. ui_indent(_mh_flags: int) -> bool # 0: ui_indent() -> bool # 1: ui_indent(_mh_flags: int) -> bool In the ordinary situation the spaces from the both sides of diffpos name are trimmed. Use this UI hint to preserve the leading spaces. )r merge_handler_params_t_ui_indentrs&*r ui_indent merge_handler_params_t.ui_indent2s::4G$GGr#r$N)$rrr8r9rrrr rmerge_handler_params_t_md_getrr merge_handler_params_t_label_get merge_handler_params_t_label_setrmerge_handler_params_t_kind_getmerge_handler_params_t_kind_setr'merge_handler_params_t_insert_after_get'merge_handler_params_t_insert_after_setr#merge_handler_params_t_mh_flags_get#merge_handler_params_t_mh_flags_setrr\rr rrrrr$r)delete_merge_handler_params_trr<r$r#rrrs-/I !#GH#J$L$LMBM*EE335E35#J'''')D.)#+J////$1L.1ZKK668Hc8 M "N L KN J H"??r#rc]tRtRt$]!RRRR7t]t]!]P]P4t R] R&]!]P]P4tR] R&]!]P ]P"4tR ] R &]!]P&]P(4tR ] R &]!]P,]P.4tR ] R &RRlt]P4tRRltRRltRRltRRltRRlt RRlt!Rt"Rt#R#)moddata_diff_helper_tihc 6VPP4#r.rLrMs&rrOmoddata_diff_helper_t.irQr#c 8VPPV4#r.rLrSs&&rrOr8irUr#rVrWr module_name netnode_namez'idbattr_info_t const *'fieldsr_nfieldsadditional_mh_flagsc$V^8dQhRRRRRR/#)rB _module_namer _netnode_name_fields'idbattr_info_t'r$)rEs"rrF"moddata_diff_helper_t.__annotate__s"Sr#c  VP\8XdRpMTp\P!V\P!WAVV44R#r.)r r6rmoddata_diff_helper_t_swiginitnew_moddata_diff_helper_t)rr@rArBrs&&&& rr\moddata_diff_helper_t.__init__sC >>2 2EE11$ % %9&&+= 9 r#c$V^8dQhRRRRRR/#rBarg0rarg1'void *'rCrir$)rEs"rrFrDs"#6h$r#c 0\P!WV4#r.)r$moddata_diff_helper_t_merge_startingrrKrLs&&&rmerge_starting$moddata_diff_helper_t.merge_startings>>t4 r#c$V^8dQhRRRRRR/#rJr$)rEs"rrFrDs'OO!4OHOOr#c 0\P!WV4#r.)r"moddata_diff_helper_t_merge_endingrPs&&&r merge_ending"moddata_diff_helper_t.merge_endings<PcP Pr#c 0\P!WW#4#r.)rmoddata_diff_helper_t_str2valr\s&&&&rstr2valmoddata_diff_helper_t.str2valrjr#c VPP4\P!V4\P !V4#r.)r rrdisown_moddata_diff_helper_trrrss&rr moddata_diff_helper_t.__disown__s/ //5}}T""r#r$N)$rrr8r9rrrr r%moddata_diff_helper_t_module_name_get%moddata_diff_helper_t_module_name_setr:r&moddata_diff_helper_t_netnode_name_get&moddata_diff_helper_t_netnode_name_setr; moddata_diff_helper_t_fields_get moddata_diff_helper_t_fields_setr<!moddata_diff_helper_t_nfields_get!moddata_diff_helper_t_nfields_setr=-moddata_diff_helper_t_additional_mh_flags_get-moddata_diff_helper_t_additional_mh_flags_setr>r\delete_moddata_diff_helper_trrQrVr]rcrhrnrr<r$r#rr6r6hs-/I !#GH --z--/K/ .. ..0L#0'/ ((*(((*F $*JHH446GS6' 55z55 77">>O  PP#r#r6c]tRtRt]!RRRR7t]t]Pt RRlt RR lt R R lt R R ltRRltRRltRRltRRlt]RRl4tRtRtRtR#)merge_node_helper_tic 6VPP4#r.rLrMs&rrOmerge_node_helper_t.rQr#c 8VPPV4#r.rLrSs&&rrOrrUr#rVrWc(V^8dQhRRRRRRRR/#) rBrK'uchar'rL 'nodeidx_t'rYrMrCrr$)rEs"rrF merge_node_helper_t.__annotate__s)WKx r#c 0\P!WW#4#)zRprint the name of the specified entry (to be used in print_diffpos_name) )r$merge_node_helper_t_print_entry_namer\s&&&&rprint_entry_name$merge_node_helper_t.print_entry_names>>t  r#c ,V^8dQhRRRRRRRRR R /#) rBrKr`rLrrYrarg3rMrCrir$)rEs"rrFrs2$$ $W$$#$'+$r#c 2\P!VWW44#)zprint the details of the specified entry usually contains multiple lines, one for each attribute or detail. (to be used in print_diffpos_details) )r'merge_node_helper_t_print_entry_detailsrrKrLrYrs&&&&&rprint_entry_details'merge_node_helper_t.print_entry_detailssAA$ $ $r#c(V^8dQhRRRRRRRR/#) rBrKr`rLrrYrMrCrir$)rEs"rrFrs*}Gr#c 0\P!WW#4#)zaget column headers for chooser (to be used in linear_diff_source_t::get_column_headers) )r&merge_node_helper_t_get_column_headersr\s&&&&rget_column_headers&merge_node_helper_t.get_column_headerss@@  r#c$V^8dQhRRRRRR/#)rBrKrrLrrCrDr$)rEs"rrFrs&MMM MtMr#c 0\P!WV4#)zr#c 2\P!WVW44#)z!map scalar/string/buffered value )rmerge_node_helper_t_map_scalarrs&&&&&r map_scalarmerge_node_helper_t.map_scalars88T  r#c ,V^8dQhRRRRRRRRRR /#) rBrKrrLrMrYrrrCrir$)rEs"rrFrs2s(#6:>r#c 2\P!WVW44#r.)rmerge_node_helper_t_map_stringrs&&&&&r map_stringmerge_node_helper_t.map_strings88T  r#c$V^8dQhRRRRRR/#)rBrKrrLrMrCrir$)rEs"rrFr s&HHGH8HtHr#c 0\P!WV4#)z|notify helper that some data was changed in the database and internal structures (e.g. caches) should be refreshed )rmerge_node_helper_t_refreshrPs&&&rrefreshmerge_node_helper_t.refresh s55d$GGr#c(V^8dQhRRRRRRRR/#)rBsrprefixeasz'eavec_t const &'rCrir$)rEs"rrFrs/KKKSK/@KDKr#c 0\P!WV4#)zcan be used by derived classes )r merge_node_helper_t_append_eavec)rrrs&&&r append_eavec merge_node_helper_t.append_eavecs::1cJJr#c VP\8XdRpMTp\P!V\P!V44R#r.)r rrmerge_node_helper_t_swiginitnew_merge_node_helper_trs& rr\merge_node_helper_t.__init__s> >>0 0EE//j # #7$$)7+ ,r#c VPP4\P!V4\P !V4#r.)r rrdisown_merge_node_helper_trrrss&rrmerge_node_helper_t.__disown__s/ --d3}}T""r#r$N)rrr8r9rrrr rdelete_merge_node_helper_trrrrrrrrr staticmethodrr\rr<r$r#rrrsq-/I !#GH!<<$M @  H KK ,#r#rct]tRtRt$]!RRRR7t]t]!]P]P4t R] R&]!]P]P4tR] R &]!]P ]P"4tR ] R &]!]P&]P(4tR ] R &RRRllt]P.tRtR#)merge_node_info_ti&c 6VPP4#r.rLrMs&rrOmerge_node_info_t.'rQr#c 8VPPV4#r.rLrSs&&rrOr'rUr#rVrWrrrtagr_ nds_flagsz'merge_node_helper_t *' node_helperNc(V^8dQhRRRRRRRR/#) rBrrrrrr_r'merge_node_helper_t'r$)rEs"rrFmerge_node_info_t.__annotate__:s/FFSFwF3FFr#c  ^\P!V\P!WW444R#r.)rmerge_node_info_t_swiginitnew_merge_node_info_t)rrrrrs&&&&&rr\merge_node_info_t.__init__:s+--dJ ! !5""&Y5E Fr#r$r.)rrr8r9rrrr rmerge_node_info_t_name_getmerge_node_info_t_name_setrrmerge_node_info_t_tag_getmerge_node_info_t_tag_setrmerge_node_info_t_nds_flags_getmerge_node_info_t_nds_flags_setr!merge_node_info_t_node_helper_get!merge_node_info_t_node_helper_setrr\delete_merge_node_info_trr<r$r#rrr&s-/I !#GH>> ""$D#$J@@,,.C.jHH224Is4+3J)):)),+K(+F"::r#rc8V^8dQhRRRRRRRRRR R R R R RR/#)rBmhp'merge_handler_params_t'rrrrrrr_rrskip_empty_nodesrDrCrcr$)rEs"rrFrFDsM77&>7s777,/77267 7r#c 4\P!WVW4WV4#)aCreate a merge handler for netnode scalar/string values :param mhp: merging parameters :param label: handler short name (to be be appended to mhp.label) :param nodename: netnode name :param tag: a tag used to access values in the netnode :param nds_flags: netnode value attributes (a combination of nds_flags_t) :param skip_empty_nodes: do not create handler in case of empty netnode :returns: diff source object (normally should be attahced to a merge handler))rcreate_nodeval_merge_handler)rrrrrrrs&&&&&&&rrrDs   2 23x  77r#c 0V^8dQhRRRRRRRRR R R R /#) rBoutz'merge_handlers_t *'rrrrvaldescz'merge_node_info_t'rrDrCrir$)rEs"rrFrFUs< # #'; # #(+ #6I # ##' #r#c2\P!WVW44#)aCreate a serie of merge handlers for netnode scalar/string values (call create_nodeval_merge_handler() for each member of VALDESC) :param out: [out] created handlers will be placed here :param mhp: merging parameters :param nodename: netnode name :param valdesc: array of handler descriptions :param skip_empty_nodes: do not create handlers for empty netnodes :returns: diff source object (normally should be attahced to a merge handler))rcreate_nodeval_merge_handlers)rrrrrs&&&&&rrrUs  3 3Ch ##r#c V^8dQhRRRR/#)rBdata_idr_rCrir$)rEs"rrFrFds>>C>4>r#c.\P!V4#r.)rdestroy_moddata_merge_handlers)rs&rrrds  4 4W ==r#c V^8dQhRRRR/#)rBrrrCrr$)rEs"rrFrFhs..O.s.r#c.\P!V4#)z9Get nice name for EA diffpos :param ea: diffpos)rget_ea_diffpos_name)rs&rrrhs  ) )" --r#)NTr)r: __future__rsysr_swig_python_version_info __package__rrrbuiltinsr ImportErrorrr%r+r5rr7rSWIG_PYTHON_LEGACY_BOOLtypingr=r>r? ida_idaapiMERGE_KIND_NETNODEMERGE_KIND_AUTOQMERGE_KIND_INFMERGE_KIND_ENCODINGSMERGE_KIND_ENCODINGS2MERGE_KIND_SCRIPTS2MERGE_KIND_SCRIPTSMERGE_KIND_CUSTDATAMERGE_KIND_CUSTCNVMERGE_KIND_ENUMSMERGE_KIND_STRUCTSMERGE_KIND_TILSMERGE_KIND_TINFOMERGE_KIND_STRMEMMERGE_KIND_UDTMEMMERGE_KIND_GHSTRCMTMERGE_KIND_STRMEMCMTMERGE_KIND_SELECTORSMERGE_KIND_STTMERGE_KIND_SEGMENTSMERGE_KIND_SEGGRPSMERGE_KIND_SEGREGSMERGE_KIND_ORPHANSMERGE_KIND_BYTEVALMERGE_KIND_FIXUPSMERGE_KIND_MAPPINGMERGE_KIND_EXPORTSMERGE_KIND_IMPORTSMERGE_KIND_PATCHESMERGE_KIND_FLAGSMERGE_KIND_EXTRACMTMERGE_KIND_AFLAGS_EAMERGE_KIND_IGNOREMICROMERGE_KIND_FILEREGIONSMERGE_KIND_HIDDENRANGESMERGE_KIND_SOURCEFILESMERGE_KIND_FUNCMERGE_KIND_FRAMEMGRMERGE_KIND_FRAMEMERGE_KIND_STKPNTSMERGE_KIND_FLOWSMERGE_KIND_CREFSMERGE_KIND_DREFSMERGE_KIND_BPTSMERGE_KIND_WATCHPOINTSMERGE_KIND_BOOKMARKSMERGE_KIND_TRYBLKSMERGE_KIND_DIRTREEMERGE_KIND_VFTABLESMERGE_KIND_SIGNATURESMERGE_KIND_PROBLEMS MERGE_KIND_UIMERGE_KIND_DEKSTOPSMERGE_KIND_NOTEPADMERGE_KIND_LOADERMERGE_KIND_DEBUGGERMERGE_KIND_DBG_MEMREGSMERGE_KIND_LUMINAMERGE_KIND_LASTMERGE_KIND_ENDMERGE_KIND_NONErHobjectrJmerge_data_t_swigregisterr!item_block_locator_t_swigregisterr#merge_handler_params_t_swigregister MH_LISTENMH_TERSEMH_UI_NODETAILS MH_UI_COMPLEXMH_UI_DP_NOLINEDIFFMH_UI_DP_SHORTNAME MH_UI_INDENTMH_UI_SPLITNAMEMH_UI_CHAR_MASKMH_UI_COMMANAMEMH_UI_COLONNAMEr6"moddata_diff_helper_t_swigregister NDS_IS_BOOL NDS_IS_EANDS_IS_RELATIVE NDS_IS_STR NDS_SUPVALNDS_BLOB NDS_EV_RANGE NDS_EV_FUNC NDS_MAP_IDX NDS_MAP_VALNDS_VAL8NDS_INC NDS_UI_NDr merge_node_helper_t_swigregisterrmerge_node_info_t_swigregisterrrrrr$r#rrPs)T#9#/"   L$L $<<%%22..**!66"88 4422 4422..22,,..0000 44!66!66** 44222222220022222222.. 44!66#::#::$<<#::,, 44..22......,,#::!662222 44"88 44((  442200 44#::00,,**,,+ \&6\&~ $$\2#6#< ,,-ABV@VV@r ../EF     ,,((  4422&& ,, ,,,,,,D#FD#N --.CD$$   ,,  " "   " "    && $$ $$ $$         G#&G#T ++,?@;;6 ))*;<7" #>.ksV VV