search for: err_str

...= null pointer. :) I'd supply a patch to fix this; but there are various ways to 'fix' this and not knowing enough about the protocol... web/swat.c: line 635 ret = local_password_change(user_name, False, add_user, enable_user, disable_user, False, new_passwd, err_str, sizeof(err_str), msg_str, sizeof(msg_str)); passdb/smbpasschange.c: line 58 BOOL local_password_change(char *user_name, BOOL trust_account, BOOL add_user, BOOL enable_user, BOOL disable_user, BOOL set_no_password, char *new_passwd, char *...

...= null pointer. :) I'd supply a patch to fix this; but there are various ways to 'fix' this and not knowing enough about the protocol... web/swat.c: line 635 ret = local_password_change(user_name, False, add_user, enable_user, disable_user, False, new_passwd, err_str, sizeof(err_str), msg_str, sizeof(msg_str)); passdb/smbpasschange.c: line 58 BOOL local_password_change(char *user_name, BOOL trust_account, BOOL add_user, BOOL enable_user, BOOL disable_user, BOOL set_no_password, char *new_passwd, char *e...

...and `%s' " "gave %d\n", add_script, add_ret)); + } else { + /* Need to add the user by other means */ + int local_flags = LOCAL_ADD_USER; /* XXX */ + BOOL ret; + pstring err_str; + pstring msg_str; + + ret = local_password_change( account, local_flags, "NEWPASS" /* XXX */, err_str, sizeof( err_str ), msg_str, sizeof(msg_str)); + if (*msg_str) + printf( msg_str ); + if (*err_str) +...

Hello We are migrating from 2.9 to 3.2 Here is some code that does not compile any more llvm::PassManager *pm; llvm::FunctionPassManager *fpm; module = llvm::ParseBitcodeFile(mb,context,&err_str); if (!module) { error() <<"Failed to load module from bitcode file: " <<err_str <<endl; exit(1); } pm = new PassManager(); pm->add(createAlwaysInlinerPass()); fpm = new FunctionPassManager(module); fpm->add(new TargetD...

We're thinking about running our own buildbot against the upstream llvm and clang sources. I'm talking to our build folks and seeing what they can allow. Maybe we can contribute some build slaves to the osuosl buildbot but I'm not sure. If we do end up having to run our own buildbot, what's the best way to integrate that into the upstream web page and status notifier? Basically,

Hi edaqa, You might need to set your TargetOptions before calling selectTarget. E.g. builder.setTargetOptions(Opts).selectTarget(...); Or you could just let EngineBuilder call selectTarget for you (which is what the no-argument version of EngineBuilder::create does): llvm::ExecutionEngine * ee = builder. setErrorStr( &errStr ). setEngineKind( llvm::EngineKind::JIT ).

Hi, Could you share how you compile IR and which version of JIT you use (Orc, MCJIT)? Could it be that you are using interpreter instead of actual JIT? Cheers, Alex. > On 5. May 2018, at 08:04, edA-qa mort-ora-y via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I'm having issues of my compiler, and JIT execution, of LLVM IR being > rather slow. It's accounting for

What exactly is your alignment settings in your LLVM struct? Something like this would tell you the alignment of "something". const llvm::DataLayout dl(theModule); size_t size = dl.getPrefTypeAlignment(something); IIn "my" compiler, I don't do anything special to align structs, so it's plausibly your specific data-layout that says that i64 only needs aligning to

I think I see a potential issue. My ExecutionEngine setup may not be using the same target as my object code emitting, and in this test case I'm running in the ExecutionEngine.  I'll go over this code to ensure I'm creating the same triple and see if that helps -- I'm assuming it will, since I can't imagine the exact same triple with clang would produce a different layout. On

...This is directly + # called by check_dtd and check_dom_against_dtd. + # We are using sys.stderr instead of print though (python3k clean). + def handle_dtd_errors(self, dtd): + # XXX: Do we really want to bail out here? + # -- sp + for err in dtd.error_log: + err_str = ''ERROR: %s\n'' % (str(err),) + sys.stderr.write(err_str) + sys.stderr.flush() sys.exit(-1) - # Here for compatibility with ValidatingApp - def get_line(self): - return -1 - - def get_column(self): - return -1 - - def dom2sax(...

I'm having issues of my compiler, and JIT execution, of LLVM IR being rather slow. It's accounting for the vast majority of my full compilation time.  I'm trying to figure out why this is happening, since it's becoming an impediment.  (Note: by slow I mean about 3s of time for only about 2K of my front-end code, 65K lines of LLVM-IR) Using valgrind I see some functions which seem

...acct_ctrl(sam_pass,(pdb_get_acct_ctrl(sam_pass)|ACB_WSTRUST)&(~A CB_NORMAL)); + } else { + pdb_set_acct_ctrl(sam_pass,(pdb_get_acct_ctrl(sam_pass)|ACB_NORMAL)&(~AC B_WSTRUST)); + } if(!pdb_update_sam_account(sam_pass, True)) { slprintf(err_str, err_str_len-1, "Failed to modify entry for user %s.\n", user_name); pdb_free_sam(sam_pass); - ---------------------------------------------------------------------- Zuse Institute Berlin, Takustrasse 7 D-14195 Berlin-Dahlem, Germany phone: +49 (30) 841 85-337, fax: +...

...me> "ldap09", flags=16, rid=0xbffffb58) at ../source3/passdb/pdb_interface.c:542 pdb = 0x80027e28 #5 0xb7d54402 in local_password_change ( user_name=0x800081c0 <user_name> "ldap09", local_flags=577, new_passwd=0x800118b8 "p4ssword", pp_err_str=0xbffffbb8, pp_msg_str=0xbffffbbc) at ../source3/passdb/passdb.c:745 tosctx = 0x8001e888 sam_pass = 0x80028100 acb = 16 rid = 0 result = {v = 0} user_exists = false ret = -1 ---Type <return> to continue, or q <return> t...

On Fri, Mar 04, 2016 at 04:16:44PM +0000, Rowland penny wrote: > On 04/03/16 09:58, Volker Lendecke wrote: > >On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: > >>On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: > >>>OK, here is the output: > >>Can you try the attached (UNTESTED!) patch? > >> > >>Thanks, >

Currently a power failure or other hard crash can cause lld leave a temporary file around. The same is true for other llvm tools. As an example, put a breakpoint in Writer.cpp:236 ("writeBuildId()") and restart the run a few times. You will get t.tmp43a735a t.tmp4deeabb t.tmp9bacdd3 t.tmpe4115c4 t.tmpeb01fff The same would happen if there was a fatal error between the