Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2009-11-26 | pidl:NDR/Parser: $size can be 'foo / 2' so we need to add '(' and ')' | Stefan Metzmacher | 1 | -1/+1 | |
foo / 5 * sizeof(bar)' isn't the same as '(foo / 2) * sizeof(bar)'. metze | |||||
2009-11-20 | Revert "Work around ndr_unpack failing on structures with relative pointers." | Stefan Metzmacher | 1 | -18/+1 | |
This reverts commit c2cdb4ad5c9398ef0d3310613107999f8d33c7ce. It's not needed anymore. metze | |||||
2009-11-20 | pidl:NDR/Parser.pm: update ndr_pull->relative_highest_offset after handling ↵ | Stefan Metzmacher | 1 | -1/+6 | |
relative pointers metze | |||||
2009-11-08 | Revert "s3: Do not reference ndr_table_<pipe> in the cli_ routines directly" | Volker Lendecke | 2 | -4/+4 | |
This reverts commit daa964013bc5d036f4da571ce22c0052ef40943a. | |||||
2009-11-08 | Revert "s3: Do not reference the ndr_tables in the server calls directly" | Volker Lendecke | 1 | -1/+1 | |
This reverts commit 98fb71782e05ae72cd6abeb38b6e0b96a50c1761. | |||||
2009-11-08 | Revert "s3: Do not reference ndr_table when calling rpc_srv_register" | Volker Lendecke | 1 | -1/+1 | |
This reverts commit 494b2aff8826947e3bd556aecb175746163da485. | |||||
2009-11-08 | s3: Do not reference ndr_table when calling rpc_srv_register | Volker Lendecke | 1 | -1/+1 | |
2009-11-08 | s3: Do not reference the ndr_tables in the server calls directly | Volker Lendecke | 1 | -1/+1 | |
This involves storing the interface table in the pipes_struct | |||||
2009-11-08 | s3: Do not reference ndr_table_<pipe> in the cli_ routines directly | Volker Lendecke | 2 | -4/+4 | |
2009-11-07 | s3: Do the printing for DEBUGLEVEL>=10 centrally | Volker Lendecke | 1 | -26/+0 | |
12 insertions(+), 10651 deletions(-) I think that says it all :-) | |||||
2009-10-13 | pidl: don't warn for compatible scalar types in unions | Andrew Tridgell | 1 | -3/+3 | |
When we have an enum that is used as a union discriminator, what matters is that the scalar mappings are the same, not if the types are the same (otherwise we get warnings about uint1632). Thanks to gd for noticing this. | |||||
2009-10-07 | tdr: teach TDR about uint1632 enums | Andrew Tridgell | 1 | -2/+4 | |
TDB doesn't have NDR64, but it needs to know how to map the new types from pidl | |||||
2009-10-07 | pidl: get the alignment right for uint1632 enums (NDR64) | Andrew Tridgell | 2 | -1/+5 | |
The default enum in NDR63 is 32 bits, not 16 bits. We need a uint1632 type to get the alignment right. | |||||
2009-10-06 | add trailer alignment to structures | Ronnie Sahlberg | 1 | -0/+14 | |
2009-10-06 | PIDL fix for using external types with wireshark backend | ronnie sahlberg | 3 | -2/+16 | |
List, Please review this patch to pidl. Basically, we need to process the wireshark conformance file BEFORE we process the idl file since this file may define external types and set the alignment for them (using the TYPE directive). Otherwise pidl will default all external types to use 4byte alignment which breaks (much more often) on NDR64 regards ronnie sahlberg From 8f86903fc353d0906bd82e72ce19c5af09beb001 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg <ronniesahlberg@gmail.com> Date: Mon, 5 Oct 2009 15:22:43 +1100 Subject: [PATCH] In the PIDL wireshark backend, we define external types in the conformance file using the TYPE directive. If we declare external types here, we must parse this file before we process the IDL file, or else these external types will all default to 4byte padding (pidl assumes all unknown types are 4byte aligned). Make sure we read the conformance file and create these new types before we parse the idl file. Signed-off-by: Ronnie Sahlberg <ronniesahlberg@gmail.com> | |||||
2009-10-03 | pidl: added int3264 as a base type | Andrew Tridgell | 2 | -0/+4 | |
This is the type used for a variable that is 32 bits for NDR32 and 64 bits for NDR64 | |||||
2009-10-02 | ndr64: added support for trailing gap alignment | Andrew Tridgell | 1 | -0/+4 | |
NDR64 has a 'trailing gap' alignment, which aligns the end of a structure on the overall structure alignment. This explains the discrepancy we had with the RPC-SAMR test and NDR64 | |||||
2009-09-29 | pidl: added union padding for NDR64 | Andrew Tridgell | 2 | -2/+17 | |
This fixes the problem with samr UserInfo16 when NDR64 is enabled | |||||
2009-09-28 | pidl: Avoid using talloc_free as function pointer, since it may be a | Jelmer Vernooij | 1 | -2/+2 | |
macro. | |||||
2009-09-26 | pidl(s4.python): Fix arguments to PyCObject_FromVoidPtr for string_array's. | Jelmer Vernooij | 1 | -1/+1 | |
Caught by Guenther. | |||||
2009-09-17 | ndr: split out ndr enum functions | Andrew Tridgell | 1 | -2/+2 | |
This allows for easier implementation of the NDR32/NDR64 split | |||||
2009-09-17 | s4-pidl: add support for NDR64 | Andrew Tridgell | 2 | -6/+9 | |
Added support for NDR64 to the samba4 pidl generator | |||||
2009-09-17 | Ensure we enclose the enum values in brackets to make the cast work. | Jeremy Allison | 1 | -0/+2 | |
Jeremy. | |||||
2009-09-17 | Fix the problem with pidl generating invalid C for enums. According | Jeremy Allison | 1 | -1/+9 | |
to the C standard an enum is guarenteed to be an (int), which means for 4 byte ints specifying a type of 0x80000000 is an invalid value. The Solaris compiler complains about this. Fix by adding an (int) cast in front of the value generation. Jeremy. | |||||
2009-08-12 | when we get an NDR error in the logs, it is useful to know where it happened | Andrew Tridgell | 1 | -5/+5 | |
2009-08-07 | pidl: parse idl 'pipe' typedefs, but print out a not supported message for now | Stefan Metzmacher | 2 | -870/+936 | |
metze | |||||
2009-08-07 | pidl: fix formatting in expr.yp | Stefan Metzmacher | 1 | -57/+59 | |
metze | |||||
2009-08-07 | pidl: fix formatting in idl.yp | Stefan Metzmacher | 1 | -427/+466 | |
metze | |||||
2009-07-31 | pidl:Samba3/ClientNDR: add support tevent_req based _send/recv() client ↵ | Stefan Metzmacher | 1 | -0/+245 | |
functions metze | |||||
2009-07-31 | pidl:Samba3/ClientNDR: rename ParseFunction => ParseFunctionSync and add ↵ | Stefan Metzmacher | 1 | -1/+8 | |
ParseFunction as glue This prepares the following ParseFunctionAsync* commits. metze | |||||
2009-07-31 | pidl:Samba3/ClientNDR: allow passing optional variable prefixes to ↵ | Stefan Metzmacher | 1 | -7/+9 | |
ParseOutputArgument() metze | |||||
2009-07-31 | pidl/Samba4.pm: allow an optional prefix passed to DeclLong() | Stefan Metzmacher | 1 | -3/+4 | |
metze | |||||
2009-07-31 | pidl:Samba4/Python: fix mapType() => mapTypeName() | Stefan Metzmacher | 1 | -1/+1 | |
This tries to fix commit 8eff9f9a3167eb0c2a4c00edf5a4cdbbc06c4dfd. The problem was: Undefined subroutine &Parse::Pidl::Samba4::Python::mapType called at /home/metze/master4/pidl/lib/Parse/Pidl/Samba4/Python.pm line 848. Jelmer: please check this. metze | |||||
2009-07-30 | python: Cope with the dom_sid2 alias in pidl's python generating code. | Jelmer Vernooij | 1 | -2/+6 | |
This fixes some problems in the samr Python bindings that pidl was (correctly) warning about. | |||||
2009-07-30 | DCE/RPC(Python): Rename py_talloc_import to py_talloc_steal. | Jelmer Vernooij | 1 | -1/+1 | |
Use py_talloc_reference in DCE/RPC code, fixes access to SAMR pipe. | |||||
2009-07-28 | pidl: import a patch to pidl made in the wireshark reporitory. | Ronnie Sahlberg | 1 | -5/+19 | |
Original commit message in wireshark SVN (rev 28961): ==== From Kovarththanan Rajaratnam: More "Cleanup header_field_info definitions" ==== Signed-off-by: Ronnie Sahlberg <ronniesahlberg@gmail.com> Signed-off-by: Stefan Metzmacher <metze@samba.org> | |||||
2009-07-27 | pidl: allow foo being on the wire after [length_is(foo)] uint8 *buffer | Stefan Metzmacher | 1 | -0/+4 | |
metze | |||||
2009-07-27 | pidl: add support for [string] on fixed size arrays. | Stefan Metzmacher | 2 | -1/+8 | |
midl also supports this: struct { long l1; [string] wchar_t str[16]; long l2; }; Where the wire size of str is encoded like a length_is() header: 4-byte offset == 0; 4-byte array length; The strings are zero terminated. metze | |||||
2009-07-19 | pidl: Print actual type names in errors about unknown origins rather than ↵ | Jelmer Vernooij | 2 | -17/+20 | |
'HASH(0x....)'. | |||||
2009-07-19 | pidl: Print proper errors when arrays don't have a specified size rather ↵ | Jelmer Vernooij | 2 | -7/+18 | |
than spewing pages of perl warnings. | |||||
2009-06-02 | Add support for double type in pidl. | Brad Hards | 2 | -0/+2 | |
Signed-off-by: Jelmer Vernooij <jelmer@samba.org> | |||||
2009-04-21 | Revert "pidl/python: Add explicit casts, fixing implicit cast warnings." | Andrew Bartlett | 1 | -1/+1 | |
It was creating new objects with bogus data. This reverts commit 210830392999691469a55f4f5e2032abcdb20b8a. | |||||
2009-04-20 | pidl:Samba4/client: fix dcerpc_ndr_request_send() callers | Stefan Metzmacher | 1 | -2/+3 | |
For samba4 you need one of this: samba/source4# make full_idl samba/source4# make clean samba# git clean -x -f metze | |||||
2009-04-20 | pidl:Samba4/client: use dcerpc_ndr_request() for sync requests | Stefan Metzmacher | 1 | -5/+7 | |
metze | |||||
2009-03-14 | Move tdr to top-level. | Jelmer Vernooij | 1 | -1/+1 | |
2009-03-04 | pidl: Don't generate variables declarations for pointless array counters. | Tim Prouty | 1 | -1/+19 | |
Code isn't generated to iterate over arrays of length 0, but the variable declarations still are. The result is 'unused variable' warnings. This only seems to be happening in one place right now, so I targeted the fix to this case, but refactoring could be done to make all variable declarations do this zero length check. Making it the default would be a much more invasive fix. Jelmer, please check! | |||||
2009-03-01 | Don't generate array iterators when the length of the array is always 0. | Jelmer Vernooij | 1 | -2/+8 | |
(bug #6140) | |||||
2009-02-25 | Only define _GNU_SOURCE if it's not defined yet. | Jelmer Vernooij | 1 | -0/+2 | |
2009-02-25 | Include header with NTSTATUS, as some IDL files use it. | Jelmer Vernooij | 1 | -0/+3 | |
2009-02-25 | Don't define _GNU_SOURCE if it's already defined on the command-line. | Jelmer Vernooij | 1 | -0/+2 | |