search for: stackframe

Hello, I have a few general questions. 1. Whether the memory contents assigned for a function are accessible after we return from that function? If yes, how can we access it? 2. Does llvm delete the stackframe assigned for a specific function, after we return from that function? 3. If not, how can we delete the stackframe or clear the memory content after we return from the function? Where do we need to change, in the assembly or llvm source? Any help would be appreciated. Thank you. Regards, Priyanka...

Hello > Would it be possible to conditionally enable the register scavenger only if > the function has a big stack? It now gets unconditionally enabled in >  SPURegisterInfo::requiresRegisterScavenging(const MachineFunction &MF). > Just checking MF.getFrameInfo()->getStackSize() here doesn't seem to be the > solution... Well, I think no. regscavenger should work well

...l errors in function prologue and epilogue insertion > -enables register scavenging for frame index elimination > and > - implements the frame index elimination for big stacks. > > Patch is made against latest svn head. > > > best regards, > Kalle Raiskila > <spu_stackframes.patch>_______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...and epilogue insertion -enables register scavenging for frame index elimination and - implements the frame index elimination for big stacks. Patch is made against latest svn head. best regards, Kalle Raiskila -------------- next part -------------- A non-text attachment was scrubbed... Name: spu_stackframes.patch Type: text/x-patch Size: 5333 bytes Desc: spu_stackframes.patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100222/018d292f/attachment.bin>

...pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8767, session=<5USPZMX3/QDAqBBU> Apr 24 16:11:14 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:15 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:15 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8769, session=<GzyeZMX3/wDAqBBU> Apr 24 16:11:15 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr...

Chris Lattner skrev: > On Feb 22, 2010, at 6:08 AM, Kalle.Raiskila at nokia.com wrote: >> currently the SPU backend does not handle big stack frames (>16*511 >> bytes) nicely. llc asserts on malformed machine instructions. >> (Assertion `MI->getOperand(OpNo).isImm() && "printDFormAddr first >> operand is not immediate") > > Sounds fine

...ging-current-function-name if you like. After some fidgeting and great help by Andrie (see the SO link; sorry I don't know his last name), it works rather well. There are, however, issues wrt do.call. Typical usage would then be: do.call(some.named.function, some.list) Now, when I look at the stackframe inside this some.named.function (or a function that is called from it), more or less like this: funcs <- sapply(2+1:sys.nframe(), function(i) sys.call(sys.parent(n=i))[[1]] ) I get strange results: contrary to the 'normal' named function calls, I don't get the function name, but I ge...

...that those posts suggested, but I am still having a problem with my dtrace application running on a heavily loaded system. I have the following lines in my D script, #pragma D option aggsize=8m #pragma D option bufsize=16m #pragma D option dynvarsize=16m #pragma D option aggrate=0 #pragma D option stackframes=MAX_STACK #pragma D option cleanrate=50Hz but still I am getting the following messages, Drop: 17458 dynamic variable drops Drop: 3426 dynamic variable drops with non-empty dirty list and the amount data that my D script is reporting, is gradually dropping. This means that the tuning...

...C level set to 20000). VBR_QUALITY and COMPLEXITY are userconfigurable, I'll ask and see what he's set them to. I must admit I'm a bit stumped as to why it's just this one user that has this problem :( I've been completely unable to replicate the problem here. I've added stackframe output on crashes to the latest testbuild, I'll have the user use that. At least then I can say what j and best_ntarget[j] is.

...ystem that smbscardd needs -lcrypto > Please let me know how. ./source3/wscript: conf.CHECK_FUNCS_IN('DES_pcbc_encrypt', 'crypto') As we already seem to check for libcrypto and store the dependency, you should be able to just add crypto to your list of deps. > no talloc stackframe at > ../../source3/passdb/machine_account_secrets.c:60, leaking memory > > So here's my second question: How do I avoid this warning? I guess you're missing a TALLOC_CTX *frame = talloc_stackframe(); in your initialisation. -slow -- Ralph Boehme, Samba Team https://s...

...>> Please let me know how. > > ./source3/wscript:??? conf.CHECK_FUNCS_IN('DES_pcbc_encrypt', 'crypto') > > As we already seem to check for libcrypto and store the dependency, > you should be able to just add crypto to your list of deps. > >> no talloc stackframe at >> ../../source3/passdb/machine_account_secrets.c:60, leaking memory >> >> So here's my second question: How do I avoid this warning? > > I guess you're missing a > > TALLOC_CTX *frame = talloc_stackframe(); > > in your initialisation. > > -slow...

...X_x86_64(lldb_private::Thread&, lldb_private::RegisterInfoInterface*, lldb_private::DataExtractor const&, lldb_private::DataExtractor const&) () from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7 #3 0x00007f81cc151e5e in ThreadElfCore::CreateRegisterContextForFrame(lldb_private::StackFrame*) () from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7 #4 0x00007f81cc1523b3 in ThreadElfCore::GetRegisterContext() () from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7 #5 0x00007f81cbfae9e2 in lldb_private::StackFrameList::GetFramesUpTo(unsigned int) () from /opt/dependency/to...

...lt;check_access+358> at /usr/local/sbin/smbd #12 0xdde58 <smbd_process+72> at /usr/local/sbin/smbd #13 0x4feb94 <main+8692> at /usr/local/sbin/smbd #14 0x64949 <_start+137> at /usr/local/sbin/smbd [2009/09/04 12:26:19, 0] lib/talloc_stack.c:talloc_tos(126) no talloc stackframe around, leaking memory [2009/09/04 12:26:19, 0] lib/fault.c:dump_core(231) dumping core in /var/log/samba/cores/smbd [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(40) =============================================================== [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(41) I...

...successfully samba3 to samba4 by using samba-tool. Today, i did "git pull", ran make clean, make and make install and the command : /usr/local/samba/bin/samba-tool domain samba3upgrade --dbdir=/root/samba3/samba/ --realm=sc.isc84.org /root/samba3/etc/smb.conf which gave : no talloc stackframe around, leaking memory You are not root or your system do not support xattr, using tdb backend for attributes. If you intend to use this provision in production, rerun the script as root on a system supporting xattrs. Reading smb.conf Provisioning Exporting account policy Exporting groups Ignorin...

Howdy, I am attempting to isolate the location of a memory leak in a 4GL program, and have hit a bit of a snag. When I LD_PRELOAD libumem and run the application server, "::findleaks -fdv" reports numerous leaks: CACHE LEAKED BUFCTL CALLER 0000000100b49068 15 0000000100ef2d50 fdcon+0x6c4 0000000100b50028 1 0000000100b72ac0 fdcon+0x6c4 0000000100b49068

...ut miliseconds if it's still valid before use. * BUG 11173: s3: libcli: smb1: Ensure we correctly finish a tevent req if the writev fails in the SMB1 case. * BUG 11175: Fix lots of winbindd zombie processes on Solaris platform. * BUG 11177: s3: libsmbclient: Add missing talloc stackframe. o Andrew Bartlett <abartlet at samba.org> * BUG 11135: backupkey: Explicitly link to gnutls and gcrypt. * BUG 11174: backupkey: Use ndr_pull_struct_blob_all(). o Ralph Boehme <slow at samba.org> * BUG 11125: vfs_fruit: Enhance handling of malformed AppleDouble files...

...ut miliseconds if it's still valid before use. * BUG 11173: s3: libcli: smb1: Ensure we correctly finish a tevent req if the writev fails in the SMB1 case. * BUG 11175: Fix lots of winbindd zombie processes on Solaris platform. * BUG 11177: s3: libsmbclient: Add missing talloc stackframe. o Andrew Bartlett <abartlet at samba.org> * BUG 11135: backupkey: Explicitly link to gnutls and gcrypt. * BUG 11174: backupkey: Use ndr_pull_struct_blob_all(). o Ralph Boehme <slow at samba.org> * BUG 11125: vfs_fruit: Enhance handling of malformed AppleDouble files...

>It should be possible to get llvm to produce very good code for the Z80... Yes, I was thinking that too. These techniques didn't exist back then, so I'm really looking forward to the point where the first regular C sources can be compiled and see the magic happening in action live :) ------------------------------------------------------------------------ *From:* Bruce Hoult

Hello, I'm upgrading samba3 to samba4 and i've the following error : > /usr/local/samba/bin/samba-tool domain samba3upgrade --dbdir=/root/samba4/samba/ --realm=sc.isc84.org /root/samba4/samba/smb.conf no talloc stackframe around, leaking memory Reading smb.conf Provisioning Exporting account policy Exporting groups *Severe DB error, sambaSamAccount can't miss the samba SIDattribute* Ignoring group 'Domain Users' S-1-5-21-1031258178-388409940-3248586695-513 listed but then not found: Unable to enumerate g...

...ut miliseconds if it's still valid before use. * BUG 11173: s3: libcli: smb1: Ensure we correctly finish a tevent req if the writev fails in the SMB1 case. * BUG 11175: Fix lots of winbindd zombie processes on Solaris platform. * BUG 11177: s3: libsmbclient: Add missing talloc stackframe. o Andrew Bartlett <abartlet at samba.org> * BUG 11135: backupkey: Explicitly link to gnutls and gcrypt. * BUG 11174: backupkey: Use ndr_pull_struct_blob_all(). o Ralph Boehme <slow at samba.org> * BUG 11125: vfs_fruit: Enhance handling of malformed AppleDouble files...