search for: free_func

I have some questions regarding how globals are represented in DS graph. Specifically, I wrote the following simple program: List *g; void alloc_func(){ g = ( List* ) malloc( sizeof( List ) ); } void free_func(){ free( g ); } int main(){ alloc_func(); free_func(); } I noticed that the DSnode for g in alloc_func is different from that of free_func and NEITHER of them had GlobalNode bit set in their types. Only the malloc bit and the incomplete bit have been set. I am completely clueless how to fig...

...s in DS graph > Sender: llvmdev-admin at cs.uiuc.edu > Date: Mon, 25 Nov 2002 01:34:14 -0600 (CST) > > > Specifically, I wrote the following simple program: > > List *g; > > void alloc_func(){ > > g = ( List* ) malloc( sizeof( List ) ); > > } > > void free_func(){ > > free( g ); > > } > > I don't have an LLVM tree available to me right now (as > tank/llvm.cs.uiuc.edu) is down, so take this with a grain of salt... > > > I noticed that the DSnode for g in alloc_func is different from that of > > free_func and NEIT...

On Fri, 22 Nov 2002, lee white baugh wrote: > do calls to exit() always have a null target-function pointer? that is > what i think i am seeing. Currently, yes. What's actually happening is that the call gets moved to the "globals graph". Essentially, this is due to the fact that the function call cannot modify the local memory graph of the current function. In cases where

> Specifically, I wrote the following simple program: > List *g; > void alloc_func(){ > g = ( List* ) malloc( sizeof( List ) ); > } > void free_func(){ > free( g ); > } I don't have an LLVM tree available to me right now (as tank/llvm.cs.uiuc.edu) is down, so take this with a grain of salt... > I noticed that the DSnode for g in alloc_func is different from that of > free_func and NEITHER of them had GlobalNode bit set in th...

...n at cs.uiuc.edu > > Date: Mon, 25 Nov 2002 01:34:14 -0600 (CST) > > > > > Specifically, I wrote the following simple program: > > > List *g; > > > void alloc_func(){ > > > g = ( List* ) malloc( sizeof( List ) ); > > > } > > > void free_func(){ > > > free( g ); > > > } > > > > I don't have an LLVM tree available to me right now (as > > tank/llvm.cs.uiuc.edu) is down, so take this with a grain of salt... > > > > > I noticed that the DSnode for g in alloc_func is different from tha...

On Mon, 23 Feb 2015, Kevin Brott wrote: > Hrm - I'll have to run this on one of my linux boxxen and then schlep the > source over - the AIX/HP-UX boxenn have an older version of the autoconf > tools and autoreconf is broken/missing ... and that seems to work. > > Now the build fails here on AIX 6.1/7.1 ... > > xlc_r -O2 -qarch=ppc -qalloca -I/usr/include

...ELPER=\"/usr/local/libexec/ssh-pkcs11-helper\" > -D_PATH_SSH_PIDDIR=\"/var/run\" -D_PATH_PRIVSEP_CHROOT_DIR=\"/var/empty\" > -DHAVE_CONFIG_H -c packet.c -o packet.o > "/usr/include/openssl/objects.h", line 1009.31: 1506-275 (S) Unexpected > text free_func encountered. > make: 1254-004 The error code from the last command is 1. I also ran into this on old GCCs. It seems to be related to include orders although I don't understand why. On a hunch I tried this which seems to fix it for me, but again I don't understand why... Does it also...

...onfiguration dump output (ssh -G). bz#2835 Portability ----------- * sshd(8): Expose details of completed authentication to PAM auth modules via SSH_AUTH_INFO_0 in the PAM environment. bz#2408 * Fix compilation problems caused by fights between zlib and OpenSSL colliding uses of "free_func" * Improve detection of unsupported compiler options. Recently these may have manifested as "unsupported -Wl,-z,retpoline" warnings during linking. * sshd(8): some sandbox support for Linux/s390 bz#2752. * regress tests: unbreak key-options.sh test on platforms without...

...onfiguration dump output (ssh -G). bz#2835 Portability ----------- * sshd(8): Expose details of completed authentication to PAM auth modules via SSH_AUTH_INFO_0 in the PAM environment. bz#2408 * Fix compilation problems caused by fights between zlib and OpenSSL colliding uses of "free_func" * Improve detection of unsupported compiler options. Recently these may have manifested as "unsupported -Wl,-z,retpoline" warnings during linking. * sshd(8): some sandbox support for Linux/s390 bz#2752. * regress tests: unbreak key-options.sh test on platforms without...

On Mon, Feb 23, 2015 at 5:27 PM, Kevin Brott <kevin.brott at gmail.com> wrote: > Just as an FYI - the whole sys/queue.h issue is impacting HP-UX 11.23 and > 11.31 as well - so we'll see how the latest fixes flush out. > > And, not to play the fool overmuch - but is there a quick howto on how > you're expecting we get the git clone pulls into a buildable state? When I

...onfiguration dump output (ssh -G). bz#2835 Portability ----------- * sshd(8): Expose details of completed authentication to PAM auth modules via SSH_AUTH_INFO_0 in the PAM environment. bz#2408 * Fix compilation problems caused by fights between zlib and OpenSSL colliding uses of "free_func" * Improve detection of unsupported compiler options. Recently these may have manifested as "unsupported -Wl,-z,retpoline" warnings during linking. * sshd(8): some sandbox support for Linux/s390 bz#2752. * regress tests: unbreak key-options.sh test on platforms without...

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address