midori preferences segmentation fault
midori Edit Preferences results, nearly every time, in: *** NSPlugin Viewer *** ERROR: rpc_end_sync called when not in sync! Segmentation fault (core dumped) This occurs since 9.1-RELEASE. All ports (midori, linux-f10-flashplugin11, nspluginwrapper, etc) are up to date. No problem with chromium. Haven't tried firefox this time. Compile time for chromium is about 6 hours. As far as I remember, firefox compile time takes even longer. What is wrong with midori ? Thank you in advance, Harald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault in FreeBSD 9.0 flockfile ()
Unga unga...@yahoo.com wrote; From: Darren Baginski kick...@yandex.com Unga unga...@yahoo.com wrote: 01.05.2012, 22:08, Unga unga...@yahoo.com: Hi all I'm getting a Segmentation fault in FreeBSD 9.0 as follows for myprog.c: Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28ebb062 in flockfile () from /lib/libc.so.7 [New Thread 29c04900 (LWP 100575/SDLTimer)] [New Thread 29c04300 (LWP 100416/myprog)] (gdb) (gdb) info threads * 2 Thread 29c04300 (LWP 100416/myprog) 0x28ebb062 in flockfile () from /lib/libc.so.7 1 Thread 29c04900 (LWP 100575/SDLTimer) 0x28e1527b in _umtx_op () from /lib/libc.so.7 (gdb) I don't use flockfile () directly in my program. Hi! Mind to share code snippet caused the problem? Hi Thanks for the reply. I have mentioned in my original post that neithe r I nor SDL use the flockfile () in the source. There was a _reason_ the prior poster asked about seeing your code. The information you provided is not adequate/sufficient for anyone to have any chance of helping you. Informationn that -is- necessary was therefore requested. What you don't use is irrelevant to solving the problem. To be any help one must figure out what you _did_ do -- which =indirectly= calls flockfile(). Your code calls something in 'libc' that calls flockfile(). You don't know what that something in your code is. Other eyes _might_ recognize it, -if- they saw what you were doing. Here is how to find out what does that calling, yourself. 1) recompile all the components of 'myprog' with the '-g' compiler option. 2) start 'script', so that you have a complete log of the debugger session. 3) load the debugger with 'myprog' as the program to be debugged. 4) set a breakpoinnt in the 'flockfile' function 5) 'run' the program 6) when it stops at flockfile() entry. use 'where' to see a stack trace. 7) 'display' each of the arguments to flockfile(). 9) go 'up' to the calling code. 9) repeat steps 7 and 8 util you reach 'your' code. 10) now 'continue' the program. If it immediately segfaults, this was the offending call. Otherwise, the program will stop aggain at another flockfile() invocation. repeat from step 7 -until- you get the segfault. If, from that debugger session, you still don't see anything wrong, post the log of the debugger session. There is a *remote* possibility that the program will run properly under the debugger, while it crashes when run directly. This has been known to happen when a program _uses_ a variable before initializing it. *IF* that happens, you will have to modify 'myprog' to add diagnostic output before and after each identified point (above) in your code that indirectly invokes flockfile() to find which is failing. In _that_ event, you =will= have to post the 'relevant' source-code from 'myprog', with the failing statement identified. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault in FreeBSD 9.0 flockfile ()
From: Robert Bonomi bon...@mail.r-bonomi.com To: freebsd-questions@freebsd.org Cc: Sent: Wednesday, May 2, 2012 6:38 AM Subject: Re: Segmentation fault in FreeBSD 9.0 flockfile () Unga unga...@yahoo.com wrote; From: Darren Baginski kick...@yandex.com Unga unga...@yahoo.com wrote: 01.05.2012, 22:08, Unga unga...@yahoo.com: Hi all I'm getting a Segmentation fault in FreeBSD 9.0 as follows for myprog.c: Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28ebb062 in flockfile () from /lib/libc.so.7 [New Thread 29c04900 (LWP 100575/SDLTimer)] [New Thread 29c04300 (LWP 100416/myprog)] (gdb) (gdb) info threads * 2 Thread 29c04300 (LWP 100416/myprog) 0x28ebb062 in flockfile () from /lib/libc.so.7 1 Thread 29c04900 (LWP 100575/SDLTimer) 0x28e1527b in _umtx_op () from /lib/libc.so.7 (gdb) I don't use flockfile () directly in my program. Hi! Mind to share code snippet caused the problem? Hi Thanks for the reply. I have mentioned in my original post that neithe r I nor SDL use the flockfile () in the source. There was a _reason_ the prior poster asked about seeing your code. The information you provided is not adequate/sufficient for anyone to have any chance of helping you. Informationn that -is- necessary was therefore requested. What you don't use is irrelevant to solving the problem. To be any help one must figure out what you _did_ do -- which =indirectly= calls flockfile(). Your code calls something in 'libc' that calls flockfile(). You don't know what that something in your code is. Other eyes _might_ recognize it, -if- they saw what you were doing. Here is how to find out what does that calling, yourself. 1) recompile all the components of 'myprog' with the '-g' compiler option. 2) start 'script', so that you have a complete log of the debugger session. 3) load the debugger with 'myprog' as the program to be debugged. 4) set a breakpoinnt in the 'flockfile' function 5) 'run' the program 6) when it stops at flockfile() entry. use 'where' to see a stack trace. 7) 'display' each of the arguments to flockfile(). 9) go 'up' to the calling code. 9) repeat steps 7 and 8 util you reach 'your' code. 10) now 'continue' the program. If it immediately segfaults, this was the offending call. Otherwise, the program will stop aggain at another flockfile() invocation. repeat from step 7 -until- you get the segfault. If, from that debugger session, you still don't see anything wrong, post the log of the debugger session. There is a *remote* possibility that the program will run properly under the debugger, while it crashes when run directly. This has been known to happen when a program _uses_ a variable before initializing it. *IF* that happens, you will have to modify 'myprog' to add diagnostic output before and after each identified point (above) in your code that indirectly invokes flockfile() to find which is failing. In _that_ event, you =will= have to post the 'relevant' source-code from 'myprog', with the failing statement identified. Hopefully I have not offended anyone with my reply :) Very sorry if I did. My this FreeBSD 9.0 box is seems very messy. I have another issue that getaddrinfo(3) doesn't accept localhost. After installing FreeBSD 9.0, I installed KDE, then realised that the existing Intel display driver does not support my Intel Sandy Bridge based GPU. So I had to patch the kernel to support KMS based latest Intel driver, upgraded to Xorg to 7.5.2, etc. etc. Whole process was done multiple times as I was new to this complex upgrade. I presume, I should erase off the hard disk and reinstall everything cleanly and then retry my programs on FreeBSD 9.0. If the problem still persists, I'll surely do a detailed debug. Pls note, whole thing works well on FreeBSD 8.1. As this is time consuming and as per existing commitments, I only try this at least in another two weeks time. I will sure let the list know the outcome. Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Segmentation fault in FreeBSD 9.0 flockfile ()
Hi all I'm getting a Segmentation fault in FreeBSD 9.0 as follows for myprog.c: Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28ebb062 in flockfile () from /lib/libc.so.7 [New Thread 29c04900 (LWP 100575/SDLTimer)] [New Thread 29c04300 (LWP 100416/myprog)] (gdb) (gdb) info threads * 2 Thread 29c04300 (LWP 100416/myprog) 0x28ebb062 in flockfile () from /lib/libc.so.7 1 Thread 29c04900 (LWP 100575/SDLTimer) 0x28e1527b in _umtx_op () from /lib/libc.so.7 (gdb) I don't use flockfile () directly in my program. I use -lpthread. Same program runs without any issue on FreeBSD 8.1. Any idea what's going on? Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault in FreeBSD 9.0 flockfile ()
Hi! Mind to share code snippet caused the problem? 01.05.2012, 22:08, Unga unga...@yahoo.com: Hi all I'm getting a Segmentation fault in FreeBSD 9.0 as follows for myprog.c: Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28ebb062 in flockfile () from /lib/libc.so.7 [New Thread 29c04900 (LWP 100575/SDLTimer)] [New Thread 29c04300 (LWP 100416/myprog)] (gdb) (gdb) info threads * 2 Thread 29c04300 (LWP 100416/myprog) 0x28ebb062 in flockfile () from /lib/libc.so.7 1 Thread 29c04900 (LWP 100575/SDLTimer) 0x28e1527b in _umtx_op () from /lib/libc.so.7 (gdb) I don't use flockfile () directly in my program. I use -lpthread. Same program runs without any issue on FreeBSD 8.1. Any idea what's going on? Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault in FreeBSD 9.0 flockfile ()
On 1 May 2012 14:08, Unga unga...@yahoo.com wrote: Hi all I'm getting a Segmentation fault in FreeBSD 9.0 as follows for myprog.c: Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28ebb062 in flockfile () from /lib/libc.so.7 [New Thread 29c04900 (LWP 100575/SDLTimer)] [New Thread 29c04300 (LWP 100416/myprog)] (gdb) (gdb) info threads * 2 Thread 29c04300 (LWP 100416/myprog) 0x28ebb062 in flockfile () from /lib/libc.so.7 1 Thread 29c04900 (LWP 100575/SDLTimer) 0x28e1527b in _umtx_op () from /lib/libc.so.7 (gdb) I use -lpthread. I doubt this is related, but using -lpthread is wrong. use -pthread (without the l). -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault in FreeBSD 9.0 flockfile ()
From: Darren Baginski kick...@yandex.com To: Unga unga...@yahoo.com Cc: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Sent: Tuesday, May 1, 2012 7:04 PM Subject: Re: Segmentation fault in FreeBSD 9.0 flockfile () Hi! Mind to share code snippet caused the problem? 01.05.2012, 22:08, Unga unga...@yahoo.com: Hi all I'm getting a Segmentation fault in FreeBSD 9.0 as follows for myprog.c: Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28ebb062 in flockfile () from /lib/libc.so.7 [New Thread 29c04900 (LWP 100575/SDLTimer)] [New Thread 29c04300 (LWP 100416/myprog)] (gdb) (gdb) info threads * 2 Thread 29c04300 (LWP 100416/myprog) 0x28ebb062 in flockfile () from /lib/libc.so.7 1 Thread 29c04900 (LWP 100575/SDLTimer) 0x28e1527b in _umtx_op () from /lib/libc.so.7 (gdb) I don't use flockfile () directly in my program. Hi Thanks for the reply. I have mentioned in my original post that neither I nor SDL use the flockfile () in the source. Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Apache segmentation fault
Upgraded php52 to php53 by pkg_delete of php5 and porinstall php52. Then I had to manually resort back to php52 by pkg_delete and then portinstall and now getting a seg fault when restarting apache22 on this FreeBSD 8.1 server. I narrowed it down to not the php module, but the two ldap modules I have in apache... mail# cat httpd.conf|grep ldap #LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so #LoadModule ldap_module libexec/apache22/mod_ldap.so With these two lines commented out, apache restarts without the seg fault. Tried to force pkg_delete on apache and then portinstall to rebuild these modules, but same issue afterward. The php module loads without error, but getting download prompts when trying to access php pages. Not getting any help from messages or httpd-error logs and all was working before I messed it up. My question is what I should try next to try and fix this issue. Should I force pkg_delete and rebuild all php packages or ldap packages? Or some other approach? Thanks for any help, Robert -- Robert rob...@webtent.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache segmentation fault
On Jan 11, 2012 12:39 PM, Robert Fitzpatrick rob...@webtent.org wrote: Upgraded php52 to php53 by pkg_delete of php5 and porinstall php52. Then I had to manually resort back to php52 by pkg_delete and then portinstall and now getting a seg fault when restarting apache22 on this FreeBSD 8.1 server. I narrowed it down to not the php module, but the two ldap modules I have in apache... mail# cat httpd.conf|grep ldap #LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so #LoadModule ldap_module libexec/apache22/mod_ldap.so With these two lines commented out, apache restarts without the seg fault. Tried to force pkg_delete on apache and then portinstall to rebuild these modules, but same issue afterward. The php module loads without error, but getting download prompts when trying to access php pages. Not getting any help from messages or httpd-error logs and all was working before I messed it up. My question is what I should try next to try and fix this issue. Should I force pkg_delete and rebuild all php packages or ldap packages? Or some other approach? Thanks for any help, Robert -- Robert rob...@webtent.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org hi, you probably need to replace php.ini ... 5.3 barfs with a 5.2 config file... not sure if the pkg thingy would wipe your config. waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache segmentation fault
On Jan 11, 2012 12:54 PM, Waitman Gobble gobble...@gmail.com wrote: On Jan 11, 2012 12:39 PM, Robert Fitzpatrick rob...@webtent.org wrote: Upgraded php52 to php53 by pkg_delete of php5 and porinstall php52. Then I had to manually resort back to php52 by pkg_delete and then portinstall and now getting a seg fault when restarting apache22 on this FreeBSD 8.1 server. I narrowed it down to not the php module, but the two ldap modules I have in apache... mail# cat httpd.conf|grep ldap #LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so #LoadModule ldap_module libexec/apache22/mod_ldap.so With these two lines commented out, apache restarts without the seg fault. Tried to force pkg_delete on apache and then portinstall to rebuild these modules, but same issue afterward. The php module loads without error, but getting download prompts when trying to access php pages. Not getting any help from messages or httpd-error logs and all was working before I messed it up. My question is what I should try next to try and fix this issue. Should I force pkg_delete and rebuild all php packages or ldap packages? Or some other approach? Thanks for any help, Robert -- Robert rob...@webtent.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org hi, you probably need to replace php.ini ... 5.3 barfs with a 5.2 config file... not sure if the pkg thingy would wipe your config. waitman sorry, somehow i missed that paragraph about commenting out the other modules... hope i didn't send you on a wild goose chase for nothing. but the behavior you describe sounds like what happens running with a mismatched php.ini... i once tried to narrow down but decided it more productive to start with a fresh ini file. i believe the problem has to do with the session config lines. that and the way it handles cgi variables (see the EPGS section) are the two biggest changes i noticed. anyway you might check if thats the issue easily by renaming php.ini.. it should run without it. (at least 5.2 would havent tried 5.3) if it runs without php.ini then that could be the problem. by the way you are restarting apache after the changes right? also verify that the modules listed in httpd.conf exist in the paths specified... hope that helps! waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache segmentation fault
On 1/11/2012 4:39 PM, Waitman Gobble wrote: sorry, somehow i missed that paragraph about commenting out the other modules... hope i didn't send you on a wild goose chase for nothing. but the behavior you describe sounds like what happens running with a mismatched php.ini... i once tried to narrow down but decided it more productive to start with a fresh ini file. i believe the problem has to do with the session config lines. that and the way it handles cgi variables (see the EPGS section) are the two biggest changes i noticed. anyway you might check if thats the issue easily by renaming php.ini.. it should run without it. (at least 5.2 would havent tried 5.3) if it runs without php.ini then that could be the problem. by the way you are restarting apache after the changes right? also verify that the modules listed in httpd.conf exist in the paths specified... hope that helps! waitman Thanks for that, found my php.ini was symlink'd to php.ini-recommended, which is now missing. PHP working now, but still no help with the segmentation fault. I have tested my ldap client pkgs and perl-LDAP to work fine, but when I uncomment those modules, I get the fault when restarting apache mail# pwd /usr/local/etc mail# cat apache22/httpd.conf|grep ldap LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so LoadModule ldap_module libexec/apache22/mod_ldap.so mail# cat apache22/httpd.conf | grep ServerRoot ServerRoot /usr/local mail# cat apache22/httpd.conf | grep ldap LoadModule authnz_ldap_module libexec/apache22/mod_authnz_ldap.so LoadModule ldap_module libexec/apache22/mod_ldap.so mail# ls -lah /usr/local/libexec/apache22/*ldap* -rwxr-xr-x 1 root wheel54K Jan 11 12:29 /usr/local/libexec/apache22/mod_authnz_ldap.so -rwxr-xr-x 1 root wheel 115K Jan 11 12:29 /usr/local/libexec/apache22/mod_ldap.so mail# rc.d/apache22 restart Performing sanity check on apache22 configuration: Syntax OK Segmentation fault (core dumped) If I comment out the two modules shown, it restarts without issue. -- Robert rob...@webtent.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault, _malloc_prefork () - debugging help needed
In the last episode (Sep 18), Unga said: I'm developing an multi-threaded application on FreeBSD. When it is running for sometime, it develops a Segmentation fault. The ddd debugger shows following: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 296c6580 (LWP 100137)] 0x28ee390e in _malloc_prefork () from /lib/libc.so.7 How could I know the exact line in source where this issue develops? If you have a full /usr/src tree extracted, you can edit /usr/src/lib/libc/Makefile and add DEBUG_FLAGS=-g at the top, then run make obj make depend make make install to install the new libc with debugging symbols. Then your debugger will show more info for functions inside libc. If you don't have a source tree checked out yet, install the devel/subversion-freebsd port, cd into /usr/src/ and run svn co svn://svn.freebsd.org/base/stable/8 . (or base/release/8.2.0, or base/stable/7 or base/head, depending on which version you want; you can browse the branches at http://svnweb.freebsd.org/base/ before you checkout anything) -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Segmentation fault, _malloc_prefork () - debugging help needed
Hi all I'm developing an multi-threaded application on FreeBSD. When it is running for sometime, it develops a Segmentation fault. The ddd debugger shows following: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 296c6580 (LWP 100137)] 0x28ee390e in _malloc_prefork () from /lib/libc.so.7 How could I know the exact line in source where this issue develops? Many thanks in advance. Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ettercap segmentation fault....
On Tue, Jul 6, 2010 at 11:21 PM, Axel Barnabas a...@ucs.com wrote: Hello, I have compiles ettercap from ports without incident. However, when I attempt to run ettercap in any way, after a short while the program crashes and I am presented with an error message which is as follows: Ooops ! This shouldn't happen... Segmentation Fault... Please recompile in debug mode, reproduce the bug and send a bugreport I have deinstalled and recompiled to program twice, yielding no results. Some additional information which may be useful- #pkg_info | grep ettercap ettercap-gtk2-0.7.3_10,1 A network sniffer/interceptor/injector/logger for switched #uname -a FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 If anyone wishes me to recompile in debug mode, you will have to tell me how; I am not familiar with the process. Axel Try this: Before building the port (if you're starting from scratch), run: Code: # cd /usr/ports/net-mgmt/ettercap # make fetch # make extract In the file /usr/ports/net-mgmt/ettercap/work/ettercap-NG-0.7.3/src/protocols/ec_tcp.c on line 119, change the following line from: Code: opt_end = (u_char *)((int)tcp + tcp-off * 4); To: Code: opt_end = (u_char *)(tcp + tcp-off * 4); ...using your favorite text editor. Then, run the typical: Code: # make config # make build # make install After all of that, give the program a run or two, and see if it's working. Let us all know. -Brandon [Refer to FreeBSD Forum Thread: http://forums.freebsd.org/showthread.php?t=15719] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
dtrace/userland causing segmentation fault
hello freebsd gurus...
i'm currently using FreeBSD 9.0-CURRENT-201101...
dtrace is enable and working
[root@ ~]# dtrace -l | tail -5
41473profile tick-1000
41474profile tick-5000
41475profile tick-1sec
41476 database5533db main
query-done
41477 database5533db main
query-start
i´m trying to use dtrace with a very basic userland program and i´m
100% of the time getting segmentation faults...
-- probes definition file --
[root@ ~]# cat simple_probes.d
provider simple {
probe loop(int);
};
-- simple program --
[root@ ~]# cat simple.c
#include stdio.h
#include simple_probes.h
int main() {
int i;
i=0;
while(1) {
printf(%d\n,i);
i++;
SIMPLE_LOOP(i);
}
return(0);
}
-- the steps i use to get the program compiled are --
[root@ ~]# dtrace -C -h -s simple_probes.d
[root@ ~]# gcc -c simple.c
[root@ ~]# dtrace -G -s simple_probes.d simple.o
[root@ ~]# gcc -lelf -o simple simple_probes.o simple.o
-- but when i run the program i always get segmentation fault :( --
[root@ ~]# ./simple
0
Segmentation fault: 11 (core dumped)
i´ve been banging my head against a wall trying to troubleshoot this
issue with obviously no success...
have any of the freebsd gurus found a similar behavior in the past
regarding userland dtrace?
any pointers/links/words of encouragement will be greatly appreciated...
regards,
javier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[solved] Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Hello and thanks for your feedback! On Tue, 2010-11-16 at 13:03 +0100, end...@gmail.com wrote: [...@pandora ~]$ php -v -c /usr/local/etc/php.ini-production PHP 5.3.2 with Suhosin-Patch (cli) (built: Jun 14 2010 18:11:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) Here's what did it for me : remove the following lines from /usr/ports/textproc/libxml2/files/patch-configure and rebuild+reinstall libxml2 @@ -20678,6 +20679,8 @@ fi fi fi ;; + *freebsd*) THREAD_LIBS= + ;; esac if test $WITH_THREADS = 1 ; then THREAD_CFLAGS=$THREAD_CFLAGS -D_REENTRANT I found this somewhere but cannot remember the thread url unfortunately... Brillant! It fixed the issue, many thanks. CC'ing both ports manager (pecl-imagick and libxml2). It would be nice if this could be fixed in the ports tree directly: are these patch lines still required by other packages? Regards, Olivier PS: something probably related is visable under http://forums.freebsd.org/archive/index.php/t-8965.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [solved] Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Hi Alex, thanks for this even better feedback. On Tue, 2010-11-16 at 15:22 +0100, Alex Dupre wrote: This is not the correct fix, the correct fix is to enable threads in php, using the appropriate OPTION. Ok, so probably this one: LINKTHR=off (default) Link thread lib (for threaded extensions) - on Is there any chance this will have other consequences (problems, incompatibilities with other php/pecl extensions) ? Or why is this off by default ? This should at least be checked when installing pecl-imagick, and I presume it will happen sometime as there is already PR about this case: http://www.freebsd.org/cgi/query-pr.cgi?pr=150996 Thanks again for your input regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Le 12 nov. 2010 à 01:04, Olivier Mueller a écrit : Good evening, On Tue, 2010-06-22 at 10:45 +0200, Olivier Mueller wrote: Problem: [...@pandora ~]$ php -v -c /usr/local/etc/php.ini-production PHP 5.3.2 with Suhosin-Patch (cli) (built: Jun 14 2010 18:11:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) Here's what did it for me : remove the following lines from /usr/ports/textproc/libxml2/files/patch-configure and rebuild+reinstall libxml2 @@ -20678,6 +20679,8 @@ fi fi fi ;; + *freebsd*) THREAD_LIBS= + ;; esac if test $WITH_THREADS = 1 ; then THREAD_CFLAGS=$THREAD_CFLAGS -D_REENTRANT I found this somewhere but cannot remember the thread url unfortunately... NZ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [solved] Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Olivier Mueller ha scritto: Brillant! It fixed the issue, many thanks. This is not the correct fix, the correct fix is to enable threads in php, using the appropriate OPTION. -- Alex Dupre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Good evening, On Tue, 2010-06-22 at 10:45 +0200, Olivier Mueller wrote: Problem: [...@pandora ~]$ php -v -c /usr/local/etc/php.ini-production PHP 5.3.2 with Suhosin-Patch (cli) (built: Jun 14 2010 18:11:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) If I comment the line extension=imagick.so in /usr/local/etc/php/extensions.ini , it works fine (but without imagick then...). I tried recompiling about nearly all related packages (png, imagemagick, php, etc.), but it didn't helped. Same if I comment some other extensions (like pdf.so, etc.). All packages are 100% uptodate, as well as the OS (7.3-RELEASE-p1 amd64), but it was previously a 7.2 system, so this may have an influence. Is anybody using pecl-imagick without this segfault at the moment? Or do you have any suggestion about what I could try? I will setup a blank 7.3 system as a VM later this week to test by myself I finally did that now (vmware-based freebsd basic system + fresh ports tree + portinstall -rvbp php5 pecl-imagick), and it is exactly the same: Segfault still displayed. Maybe it's related to the WITHOUT_X11=yes in my make.conf ? I'll try again without that parameter later. Here are the ports list and gdb output, maybe someone will have an idea why it is reacting like that? : [r...@bsdbox73 ~]# php -v PHP 5.3.3 with Suhosin-Patch (cli) (built: Nov 11 2010 14:40:34) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) [r...@bsdbox73 ~]# [r...@bsdbox73 ~]# gdb php php.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /lib/libz.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.4 Reading symbols from /usr/local/lib/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x000803190820 in ?? () (gdb) (gdb) bt #0 0x000803190820 in ?? () #1 0x000800db17d5 in xmlFreeMutex () from /usr/local/lib/libxml2.so.5 #2 0x000800db1215 in xmlCleanupGlobals () from /usr/local/lib/libxml2.so.5 #3 0x000800d49d3a in xmlCleanupParser () from /usr/local/lib/libxml2.so.5 #4 0x0044ff28 in php_libxml_shutdown () #5 0x0044ff59 in zm_shutdown_libxml () #6 0x00558f2f in module_destructor () #7 0x0056061a in zend_hash_apply_deleter () #8 0x00560888 in zend_hash_graceful_reverse_destroy () #9 0x00554357 in zend_shutdown () #10 0x005005f5 in php_module_shutdown () #11 0x005dea4f in main () #12 0x004186de in _start () #13 0x000800781000 in ?? () #14 0x in ?? () #15 0x in ?? () [...] ---Type return to continue, or q return to quit---q Quit (gdb) [r...@bsdbox73 ~]# cat /etc//make.conf # om/20080318 WITHOUT_X11=yes [r...@bsdbox73 ~]# cat /usr/local/etc/php/extensions.ini extension=imagick.so [r...@bsdbox73 ~]# uname -a FreeBSD bsdbox73.omx.ch 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 05:25:24 UTC 2010 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 [r...@bsdbox73 ~]# pkg_info ImageMagick-nox11-6.6.4.10 Image processing tools apache-2.0.64 Version 2.0.x of Apache web server with prefork MPM. apr-0.9.19.0.9.19 Apache Portability Library autoconf-2.68 Automatically configure source code on many Un*x platforms autoconf-wrapper-20071109 Wrapper script for GNU autoconf automake-1.11.1 GNU Standards-compliant Makefile generator (1.11) automake-wrapper-20071109 Wrapper script for GNU automake bash-4.0.35 The GNU Project's Bourne Again SHell cups-client-1.4.4 Common UNIX Printing System: Library cups
pyglet font load segmentation fault
Dear all,
I posted about this problem a few months ago and have been scouring
the web ever since but I cannot find the slightest hint at a solution.
Actually, it seems that nobody else has reported a similar problem,
which I find really weird since the function is such a basic one in
pyglet -- quoting Zoolander, I feel like I am taking crazy pills!
The problem is that I cannot use the pyglet.font.load() function at
all without causing a segmentation fault:
python
import pyglet
arial = pyglet.font.load('Arial')
Segmentation fault
My system is running FreeBSD 8.1/amd64 with an Nvidia GeForce 9500GT
and the latest driver from Nvidia (256.53), and with all the ports
up-to-date as of today.
python26-2.6.5_1 was compiled with standard options:
WITH_THREADS=true
WITHOUT_HUGE_STACK_SIZE=true
WITHOUT_SEM=true
WITHOUT_PTH=true
WITH_UCS4=true
WITH_PYMALLOC=true
WITH_IPV6=true
WITHOUT_FPECTL=true
Any help would be tremendously appreciated,
thanks in advance
giuseppe
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ettercap segmentation fault....
Hello, I have compiles ettercap from ports without incident. However, when I attempt to run ettercap in any way, after a short while the program crashes and I am presented with an error message which is as follows: Ooops ! This shouldn't happen... Segmentation Fault... Please recompile in debug mode, reproduce the bug and send a bugreport I have deinstalled and recompiled to program twice, yielding no results. Some additional information which may be useful- #pkg_info | grep ettercap ettercap-gtk2-0.7.3_10,1 A network sniffer/interceptor/injector/logger for switched #uname -a FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 If anyone wishes me to recompile in debug mode, you will have to tell me how; I am not familiar with the process. Axel___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Eclipse causes segmentation fault in Java
Hey, I have a fresh FBSD 8-Stable/AMD64 installation and I want to run Eclipse. This is what I get: [starlight] ~ eclipse realpath: : No such file or directory # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000825d6d985, pid=11170, tid=0xa0ae40 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-p4-root_13_may_2010_21_53-b00 mixed mode) # Problematic frame: # C [libglib-2.0.so.0+0x18985] g_base64_encode_step+0xe5 # # An error report file with more information is saved as hs_err_pid11170.log # # Please submit bug reports to freebsd-j...@freebsd.org # Mentioned file is attached. I'm using jdk16 from ports. I have also tried with diablo-jdk from ports with exactly the same result. java -version realpath: : No such file or directory java version 1.6.0_03-p4 Java(TM) SE Runtime Environment (build 1.6.0_03-p4-root_13_may_2010_21_53-b00) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-p4-root_13_may_2010_21_53-b00, mixed mode) After Eclipse crashes like this, my system becomes unusably slow: in top I can see the java process using 43 GB of memory (the SIZE column) and being in STOP state. Java is then slowly consuming my physical memory until I reboot. It is apparantely trying to dump a core: ls -lh ~/java.core -rw--- 1 oxyd oxyd43G May 13 21:15 /usr/home/oxyd/java.core I need to say this is the largest coredump I've ever seen. Doing sysctl kern.coredump=0 and retrying Eclipse produces the same error but doesn't hang my machine. I'm also unsure about the realpath: : No such file or directory message that appears in the output, but I don't know what it means and Google doesn't help much. I'll be happy to hear any suggestions. ~ Ondra # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000825d6d985, pid=11170, tid=0xa0ae40 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-p4-root_13_may_2010_21_53-b00 mixed mode) # Problematic frame: # C [libglib-2.0.so.0+0x18985] g_base64_encode_step+0xe5 # # Please submit bug reports to freebsd-j...@freebsd.org # --- T H R E A D --- Current thread (0x000800a8e000): JavaThread main [_thread_in_native, id=10530368] siginfo:si_signo=11, si_errno=0, si_code=2, si_addr=0x000825a0d000 Registers: RAX=0x, RBX=0x7fbec69c, RCX=0x000825dd1740, RDX=0x RSP=0x7fbec660, RBP=0x00082a00, RSI=0x0007, RDI=0x000825a0d000 R8 =0x00082a70f6a8, R9 =0x7fbec698, R10=0x, R11=0x000825a0cffe R12=0x0010254c2346, R13=0x, R14=0x, R15=0x0008257f1b50 RIP=0x000825d6d985, EFL=0x0001, ERR=0x0004 TRAPNO=0x000c Top of Stack: (sp=0x7fbec660) 0x7fbec660: 7fbec698 00080c48 0x7fbec670: 7fbec69c 00082a00 0x7fbec680: 0008254c1700 000825d6ded3 0x7fbec690: 7fbec774 0x7fbec6a0: 0008009a8c20 00082567d600 0x7fbec6b0: 7fbfd910 0x7fbec6c0: 0008257f1ba0 000829ebca35 0x7fbec6d0: 000829ebb190 000829662280 0x7fbec6e0: 000829662289 0010 0x7fbec6f0: 0x7fbec700: 0x7fbec710: 0008009a8c20 0008007ee3f9 0x7fbec720: 00080c48 0008254c1700 0x7fbec730: 000829662220 0008257b22c0 0x7fbec740: 0008257f7fb0 0008256a1b00 0x7fbec750: 000800a36800 000800ab1880 0x7fbec760: 000800a9b800 000829646ed0 0x7fbec770: ffbfd910 0020 0x7fbec780: 00060020 0008009a8c20 0x7fbec790: 00082567d600 0x7fbec7a0: 7fbfd910 000828306150 0x7fbec7b0: 0x7fbec7c0: 0x7fbec7d0: 0x7fbec7e0: 0x7fbec7f0: 0x7fbec800: 0x7fbec810: 0x7fbec820: 0x7fbec830: 0x7fbec840: 0x7fbec850: Instructions: (pc=0x000825d6d985) 0x000825d6d975: b6 17 48 83 c7 01 44 89 d0 48 8d 0d bb 3d 06 00 0x000825d6d985: 0f b6 37 c1 f8 02 41 83 e2 03 4c 8d 5f 01 48 98 Stack: [0x7faff000,0x7fbff000), sp=0x7fbec660, free space=949k Native frames: (J=compiled Java code,
Re: Eclipse causes segmentation fault in Java
On Thu, May 13, 2010 at 11:10:42PM +0200, Ondrej Majerech wrote: Hey, I have a fresh FBSD 8-Stable/AMD64 installation and I want to run Eclipse. This is what I get: [starlight] ~ eclipse realpath: : No such file or directory # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000825d6d985, pid=11170, tid=0xa0ae40 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-p4-root_13_may_2010_21_53-b00 mixed mode) # Problematic frame: # C [libglib-2.0.so.0+0x18985] g_base64_encode_step+0xe5 # # An error report file with more information is saved as hs_err_pid11170.log # # Please submit bug reports to freebsd-j...@freebsd.org # At a guess, you recently upgraded to GNOME 2.30; and since it's been crashing. I just started seeing this myself since I updated yesterday. Cheers. -- Jonathan Chen j...@chen.org.nz -- Vini, vidi, velcro... I came, I saw, I stuck around ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Eclipse causes segmentation fault in Java
Jonathan Chen wrote: On Thu, May 13, 2010 at 11:10:42PM +0200, Ondrej Majerech wrote: At a guess, you recently upgraded to GNOME 2.30; and since it's been crashing. I just started seeing this myself since I updated yesterday. Cheers. This is a fresh install, so I didn't yet have the chance to upgrade anything -- everything is a fresh, first-time install. But yeah, it appears to be the case. Eclipse pulled libgnome-2.30.0 as a dependency (among others). Perhaps rebuilding Eclipse with WITHOUT_GNOMEVFS=yes is worth a try. I'm not a Gnome user anyway. ~ Ondra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports/devel/protobuf: Segmentation fault in mmap in some applications
On 01/07/10 19:56, Pieter de Goeje wrote:
On Thursday 07 January 2010 10:02:36 O. Hartmann wrote:
On 01/07/10 01:41, Pieter de Goeje wrote:
On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
Dear Sirs,
We use a software package for scientific imagery processing from USGS,
ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
3.1.21 and since this version, the software intensively uses
libprotobuf.so.
While we can use ISIS 3.1.20 very well under FreeBSD 8.0/amd64, it is
impossible to use the software with version no. 3.1.21, which seems to
have some issues wih libprotobuf.so. Every client out of this ISIS3
package crashes with a segmentation fault and as far as I can judge the
situation, there is a problem with libprotobuf.so, against which all
clients out of ISIS 3.1.21 are linked.
Perhaps the ISIS package was developed using a different (older?) version
of Google's protocol buffers. Compiling protobuf from source is quite
easy on FreeBSD. You can find the source here:
http://code.google.com/p/protobuf/downloads/list
I would start by trying version 2.1.0 and 2.2.0a.
I searched for help on the ISIS3-support forum and realised that some
Apple OS X guys have had similar problems, but those threads where
closed immediately or got relative senseless response.
In our case, we compile every necessary library and prerequisite
software package (mostly Qt4 libs) from ports. This works great with
some tweaks for FreeBSD in make/config.freebsd (which I derived from
some linux and/or OS X config files).
Now I'm floating like a dead man i the water. Below I provide q gdb
output of the qview-client (the same is with all other clients, like
photrim etc. for those familiar with the software package).
A backtrace ('bt' at the gdb prompt) might contain more useful
information.
Additionaly, I provide a truss-output, that stops at mmap issues.
Well, if someone could provide me with some advance debugging hints I
would appreaciate them. I'm pretty sure he problem is located within the
libprotobuf library or the way it is treated, but this is a guess of a
non-developer.
Thanks very much in advance.
Please reply also to this email address, since I'm not subscriber of the
list I post to.
Oliver
- Pieter
Hello Pieter,
ISIS3 utilises the very same revision of libprotobuf as FreeBSD has in
the ports repositorium (libprotobuf.so.4.0.0, aka protobuf-2.2.0). The
backtrace follows, it is a little bit lengthy ...
Ok, I can reproduce this locally. The cause is incorrect compiler flags.
Basically one must use `pkg-config --cflags protobuf` to get the correct
CFLAGS and `pkg-config --libs protobuf` for the correct libraries.
Most likely one or both of the following were missing during the
compilation/linking of ISIS: -D_THREAD_SAFE -pthread
Regards,
Pieter
You're right. Thank you very much. After applying the output of
pkg-config --libs protobuf to the proper make file, everythng went as
expected!
Regards and thanks,
Oliver
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports/devel/protobuf: Segmentation fault in mmap in some applications
On 01/07/10 01:41, Pieter de Goeje wrote:
On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
Dear Sirs,
We use a software package for scientific imagery processing from USGS,
ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
3.1.21 and since this version, the software intensively uses
libprotobuf.so.
While we can use ISIS 3.1.20 very well under FreeBSD 8.0/amd64, it is
impossible to use the software with version no. 3.1.21, which seems to
have some issues wih libprotobuf.so. Every client out of this ISIS3
package crashes with a segmentation fault and as far as I can judge the
situation, there is a problem with libprotobuf.so, against which all
clients out of ISIS 3.1.21 are linked.
Perhaps the ISIS package was developed using a different (older?) version of
Google's protocol buffers. Compiling protobuf from source is quite easy on
FreeBSD. You can find the source here:
http://code.google.com/p/protobuf/downloads/list
I would start by trying version 2.1.0 and 2.2.0a.
I searched for help on the ISIS3-support forum and realised that some
Apple OS X guys have had similar problems, but those threads where
closed immediately or got relative senseless response.
In our case, we compile every necessary library and prerequisite
software package (mostly Qt4 libs) from ports. This works great with
some tweaks for FreeBSD in make/config.freebsd (which I derived from
some linux and/or OS X config files).
Now I'm floating like a dead man i the water. Below I provide q gdb
output of the qview-client (the same is with all other clients, like
photrim etc. for those familiar with the software package).
A backtrace ('bt' at the gdb prompt) might contain more useful information.
Additionaly, I provide a truss-output, that stops at mmap issues.
Well, if someone could provide me with some advance debugging hints I
would appreaciate them. I'm pretty sure he problem is located within the
libprotobuf library or the way it is treated, but this is a guess of a
non-developer.
Thanks very much in advance.
Please reply also to this email address, since I'm not subscriber of the
list I post to.
Oliver
- Pieter
Hello Pieter,
ISIS3 utilises the very same revision of libprotobuf as FreeBSD has in
the ports repositorium (libprotobuf.so.4.0.0, aka protobuf-2.2.0). The
backtrace follows, it is a little bit lengthy ...
(gdb) bt
#0 0x000805a2f2c8 in std::_Rb_treestd::string,
std::pairstd::string const, std::pairvoid const*, int ,
std::_Select1ststd::pairstd:: tring const, std::pairvoid const*, int
, std::lessstd::string, std::allocatorstd::pairstd::string
const, std::pairvoid const*, int::_M_insert_unique () from
/usr/local/lib/libprotobuf.so.4
#1 0x000805a326c6 in
google::protobuf::InsertIfNotPresentstd::mapstd::string,
std::pairvoid const*, int, std::lessstd::string, std::a
locatorstd::pairstd::string const, std::pairvoid const*, int ,
std::string, std::pairvoid const*, int ()
from /usr/local/lib/libprotobuf.so.4
#2 0x000805a32d4f in
google::protobuf::SimpleDescriptorDatabase::DescriptorIndexstd::pairvoid
const*, int ::AddFile ()
from /usr/local/lib/libprotobuf.so.4
#3 0x000805a2df86 in
google::protobuf::EncodedDescriptorDatabase::Add () from
/usr/local/lib/libprotobuf.so.4
#4 0x0008059ed8fd in
google::protobuf::DescriptorPool::InternalAddGeneratedFile () from
/usr/local/lib/libprotobuf.so.4
#5 0x000805a16218 in
google::protobuf::protobuf_AddDesc_google_2fprotobuf_2fdescriptor_2eproto ()
from /usr/local/lib/libprotobuf.so.4
#6 0x000805a168a5 in __static_initialization_and_destruction_0 ()
from /usr/local/lib/libprotobuf.so.4
#7 0x000805a64aab in __do_global_ctors_aux () from
/usr/local/lib/libprotobuf.so.4
#8 0x0008059d00f6 in _init () from /usr/local/lib/libprotobuf.so.4
#9 0x00080064bc70 in ?? () from /libexec/ld-elf.so.1
#10 0x00080052582b in dlsym () from /libexec/ld-elf.so.1
#11 0x000800526b85 in dlopen () from /libexec/ld-elf.so.1
#12 0x0008005217a9 in ?? () from /libexec/ld-elf.so.1
#13 0x in ?? ()
#14 0x in ?? ()
#15 0x in ?? ()
#16 0x in ?? ()
#17 0x0001 in ?? ()
#18 0x7fffe800 in ?? ()
#19 0x in ?? ()
#20 0x7fffe806 in ?? ()
#21 0x7fffe822 in ?? ()
#22 0x7fffe847 in ?? ()
#23 0x7fffe852 in ?? ()
#24 0x7fffe86c in ?? ()
#25 0x7fffe879 in ?? ()
#26 0x7fffe899 in ?? ()
#27 0x7fffe8c7 in ?? ()
#28 0x7fffe8d9 in ?? ()
#29 0x7fffe8f0 in ?? ()
#30 0x7fffe907 in ?? ()
#31 0x7fffe927 in ?? ()
#32 0x7fffe936 in ?? ()
#33 0x7fffe943 in ?? ()
#34 0x7fffe95d in ?? ()
#35 0x7fffec8e in ?? ()
#36 0x7fffecb1 in ?? ()
#37 0x7fffecbc in ?? ()
#38 0x7fffecd1 in ?? ()
#39 0x7fffed99 in ?? ()
#40 0x7fffedb2 in ?? ()
#41 0x7fffedce
Re: ports/devel/protobuf: Segmentation fault in mmap in some applications
On Thursday 07 January 2010 10:02:36 O. Hartmann wrote:
On 01/07/10 01:41, Pieter de Goeje wrote:
On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
Dear Sirs,
We use a software package for scientific imagery processing from USGS,
ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
3.1.21 and since this version, the software intensively uses
libprotobuf.so.
While we can use ISIS 3.1.20 very well under FreeBSD 8.0/amd64, it is
impossible to use the software with version no. 3.1.21, which seems to
have some issues wih libprotobuf.so. Every client out of this ISIS3
package crashes with a segmentation fault and as far as I can judge the
situation, there is a problem with libprotobuf.so, against which all
clients out of ISIS 3.1.21 are linked.
Perhaps the ISIS package was developed using a different (older?) version
of Google's protocol buffers. Compiling protobuf from source is quite
easy on FreeBSD. You can find the source here:
http://code.google.com/p/protobuf/downloads/list
I would start by trying version 2.1.0 and 2.2.0a.
I searched for help on the ISIS3-support forum and realised that some
Apple OS X guys have had similar problems, but those threads where
closed immediately or got relative senseless response.
In our case, we compile every necessary library and prerequisite
software package (mostly Qt4 libs) from ports. This works great with
some tweaks for FreeBSD in make/config.freebsd (which I derived from
some linux and/or OS X config files).
Now I'm floating like a dead man i the water. Below I provide q gdb
output of the qview-client (the same is with all other clients, like
photrim etc. for those familiar with the software package).
A backtrace ('bt' at the gdb prompt) might contain more useful
information.
Additionaly, I provide a truss-output, that stops at mmap issues.
Well, if someone could provide me with some advance debugging hints I
would appreaciate them. I'm pretty sure he problem is located within the
libprotobuf library or the way it is treated, but this is a guess of a
non-developer.
Thanks very much in advance.
Please reply also to this email address, since I'm not subscriber of the
list I post to.
Oliver
- Pieter
Hello Pieter,
ISIS3 utilises the very same revision of libprotobuf as FreeBSD has in
the ports repositorium (libprotobuf.so.4.0.0, aka protobuf-2.2.0). The
backtrace follows, it is a little bit lengthy ...
Ok, I can reproduce this locally. The cause is incorrect compiler flags.
Basically one must use `pkg-config --cflags protobuf` to get the correct
CFLAGS and `pkg-config --libs protobuf` for the correct libraries.
Most likely one or both of the following were missing during the
compilation/linking of ISIS: -D_THREAD_SAFE -pthread
Regards,
Pieter
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports/devel/protobuf: Segmentation fault in mmap in some applications
On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
Dear Sirs,
We use a software package for scientific imagery processing from USGS,
ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
3.1.21 and since this version, the software intensively uses
libprotobuf.so.
While we can use ISIS 3.1.20 very well under FreeBSD 8.0/amd64, it is
impossible to use the software with version no. 3.1.21, which seems to
have some issues wih libprotobuf.so. Every client out of this ISIS3
package crashes with a segmentation fault and as far as I can judge the
situation, there is a problem with libprotobuf.so, against which all
clients out of ISIS 3.1.21 are linked.
Perhaps the ISIS package was developed using a different (older?) version of
Google's protocol buffers. Compiling protobuf from source is quite easy on
FreeBSD. You can find the source here:
http://code.google.com/p/protobuf/downloads/list
I would start by trying version 2.1.0 and 2.2.0a.
I searched for help on the ISIS3-support forum and realised that some
Apple OS X guys have had similar problems, but those threads where
closed immediately or got relative senseless response.
In our case, we compile every necessary library and prerequisite
software package (mostly Qt4 libs) from ports. This works great with
some tweaks for FreeBSD in make/config.freebsd (which I derived from
some linux and/or OS X config files).
Now I'm floating like a dead man i the water. Below I provide q gdb
output of the qview-client (the same is with all other clients, like
photrim etc. for those familiar with the software package).
A backtrace ('bt' at the gdb prompt) might contain more useful information.
Additionaly, I provide a truss-output, that stops at mmap issues.
Well, if someone could provide me with some advance debugging hints I
would appreaciate them. I'm pretty sure he problem is located within the
libprotobuf library or the way it is treated, but this is a guess of a
non-developer.
Thanks very much in advance.
Please reply also to this email address, since I'm not subscriber of the
list I post to.
Oliver
- Pieter
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
STOP state in top + segmentation fault and core dump?
Hi, When I run many heavily multi-threaded (1000+ threads/process) and memory intensive (1800 MB+/process) processes on FreeBSD 8.0 amd64, some of them get in STOP state in top and then seg fault and core dump. Are stop states in top caused by seg faults or it is the OS that stops the processes because they exceed some limit? I do not see any message about any limit being exceeded. The machine has 12GB of memory so it should be able to sustain 4 processes using 1800MB each of memory I guess (I have 12 GB of swap space anyway but it stays unused). Everything runs fine if I run a single process and I have never encountered such problems when running these on Linux. Anyone has an idea? I am using the default limits right now: limit cputime unlimited filesize unlimited datasize 33554432 kbytes stacksize524288 kbytes coredumpsize unlimited memoryuseunlimited vmemoryuse unlimited descriptors 11095 memorylocked unlimited maxproc 5547 sbsize unlimited swapsize unlimited Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
w3m - Segmentation fault
Hello, I try today install port w3m (www/w3m) and got segmentation fault. Is somone else have such trouble? FreeBSD 7.2-RELEASE, AMD64. # make install clean ... cc -I. -I. -O2 -fno-strict-aliasing -pipe -I/usr/include/openssl -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -DAUXBIN_DIR=\/usr/local/libexec/w3m\ -DCGIBIN_DIR=\/usr/local/libexec/w3m/cgi-bin\ -DHELP_DIR=\/usr/local/share/w3m\ -DETC_DIR=\/usr/local/etc\ -DCONF_DIR=\/usr/local/etc/w3m\ -DRC_DIR=\~/.w3m\ -DLOCALEDIR=\/usr/local/share/locale\ -c myctype.c cc -I. -I. -O2 -fno-strict-aliasing -pipe -I/usr/include/openssl -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -DAUXBIN_DIR=\/usr/local/libexec/w3m\ -DCGIBIN_DIR=\/usr/local/libexec/w3m/cgi-bin\ -DHELP_DIR=\/usr/local/share/w3m\ -DETC_DIR=\/usr/local/etc\ -DCONF_DIR=\/usr/local/etc/w3m\ -DRC_DIR=\~/.w3m\ -DLOCALEDIR=\/usr/local/share/locale\ -c hash.c ar rv libindep.a Str.o indep.o regex.o textlist.o parsetag.o myctype.o hash.o ar: creating libindep.a a - Str.o a - indep.o a - regex.o a - textlist.o a - parsetag.o a - myctype.o a - hash.o ranlib libindep.a cc -I. -I. -O2 -fno-strict-aliasing -pipe -I/usr/include/openssl -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -DAUXBIN_DIR=\/usr/local/libexec/w3m\ -DCGIBIN_DIR=\/usr/local/libexec/w3m/cgi-bin\ -DHELP_DIR=\/usr/local/share/w3m\ -DETC_DIR=\/usr/local/etc\ -DCONF_DIR=\/usr/local/etc/w3m\ -DRC_DIR=\~/.w3m\ -DLOCALEDIR=\/usr/local/share/locale\ -o mktable mktable.o dummy.o -L/usr/local/lib -lm -L. -lindep -L/usr/local/lib -lgc sort funcname.tab | nawk -f ./functable.awk functable.tab ./mktable 100 functable.tab functable.c Segmentation fault (core dumped) *** Error code 139 Stop in /usr/ports/www/w3m/work/w3m-0.5.2. *** Error code 1 Stop in /usr/ports/www/w3m. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Segmentation fault: 11 (core dumped)
r...@mx1 ~ 496$ csh Segmentation fault: 11 (core dumped) r...@mx1 ~ 497$ i even updated all my system to latest -RELEASE r...@mx1 ~ 499$ uname -a FreeBSD mx1.alexus.biz 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #3: Sun Mar 29 05:42:35 UTC 2009 ale...@dd.alexus.org:/usr/obj/usr/src/sys/GENERIC amd64 r...@mx1 ~ 500$ I've had that on other systems as well, this isn't the first one I'm having this issue... -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault: 11 (core dumped)
On Mon, Apr 6, 2009 at 3:03 PM, alexus ale...@gmail.com wrote: r...@mx1 ~ 496$ csh Segmentation fault: 11 (core dumped) r...@mx1 ~ 497$ Segmentation Fault 11 is typically indicative of hardware failure (CPU, RAM, motherboard). Can you run memtest86+ and test that theory? -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault: 11 (core dumped)
On Mon, Apr 6, 2009 at 3:09 PM, Glen Barber glen.j.bar...@gmail.com wrote: On Mon, Apr 6, 2009 at 3:03 PM, alexus ale...@gmail.com wrote: r...@mx1 ~ 496$ csh Segmentation fault: 11 (core dumped) r...@mx1 ~ 497$ Segmentation Fault 11 is typically indicative of hardware failure (CPU, RAM, motherboard). Can you run memtest86+ and test that theory? I doubt that it has anything to do with hardware, as a) everything else works fine except for this thing b) i'm getting same type of behavior on multiple systems (some of these systems are high end boxes, some of them are low end) -- Glen Barber -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ldapadd Crashed with Segmentation Fault
I had the same problem (also slapcat ended with seg fault 11). And the siolution was to minimize the config options (i did not need all of them). I only build OpenLDAP with the SASL,BDB and PERL options and worked for me Reg,Danny - Original Message - From: Hong ljf...@sdf.lonestar.org To: FreeBSD Questions List freebsd-questions@freebsd.org Sent: Wednesday, March 11, 2009 5:15 AM Subject: Ldapadd Crashed with Segmentation Fault Hi, I was playing with OpenLDAP installed on FreeBSD 7.1-RELEASE installed through the port system. The configuration file /usr/local/etc/slapd.conf was edited: ... databasebdb #suffix dc=my-domain,dc=com #rootdn cn=Manager,dc=my-domain,dc=com suffix dc=example,dc=com rootdn cn=Manager,dc=example,dc=com ... I created a test LDIF file named test1.ldif: dn: dc=example,dc=com objectclass: dcObject objectclass: organization o: Example Company dc: example dn: cn=Manager,dc=example,dc=com objectClass: organizationalRole cn: Manager Then I used ldapadd to add the new entries in the LDIF file: # ldapadd -x -D cn=Manager,dc=example,dc=com -W -f test1.ldif Enter LDAP Password: adding new entry dc=example,dc=com adding new entry cn=Manager,dc=example,dc=com Segmentation fault: 11 (core dumped) Any idea what went wrong? Hong ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.9/1992 - Release Date: 03/09/09 19:20:00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ldapadd Crashed with Segmentation Fault
Hi, I was playing with OpenLDAP installed on FreeBSD 7.1-RELEASE installed through the port system. The configuration file /usr/local/etc/slapd.conf was edited: ... databasebdb #suffix dc=my-domain,dc=com #rootdn cn=Manager,dc=my-domain,dc=com suffix dc=example,dc=com rootdn cn=Manager,dc=example,dc=com ... I created a test LDIF file named test1.ldif: dn: dc=example,dc=com objectclass: dcObject objectclass: organization o: Example Company dc: example dn: cn=Manager,dc=example,dc=com objectClass: organizationalRole cn: Manager Then I used ldapadd to add the new entries in the LDIF file: # ldapadd -x -D cn=Manager,dc=example,dc=com -W -f test1.ldif Enter LDAP Password: adding new entry dc=example,dc=com adding new entry cn=Manager,dc=example,dc=com Segmentation fault: 11 (core dumped) Any idea what went wrong? Hong ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ldapadd Crashed with Segmentation Fault
On Tue, 2009-03-10 at 21:15 -0700, Hong wrote: Hi, I was playing with OpenLDAP installed on FreeBSD 7.1-RELEASE installed through the port system. The configuration file /usr/local/etc/slapd.conf was edited: ... databasebdb #suffix dc=my-domain,dc=com #rootdn cn=Manager,dc=my-domain,dc=com suffix dc=example,dc=com rootdn cn=Manager,dc=example,dc=com ... I created a test LDIF file named test1.ldif: dn: dc=example,dc=com objectclass: dcObject objectclass: organization o: Example Company dc: example dn: cn=Manager,dc=example,dc=com objectClass: organizationalRole cn: Manager Then I used ldapadd to add the new entries in the LDIF file: # ldapadd -x -D cn=Manager,dc=example,dc=com -W -f test1.ldif Enter LDAP Password: adding new entry dc=example,dc=com adding new entry cn=Manager,dc=example,dc=com Segmentation fault: 11 (core dumped) Any idea what went wrong? Hong Why it crashed? don't know. Most segfaults in my experience (few and far between) are due to compiled options that crash it. My experience with OpenLDAP has taught me the rootdn specified in slapd.conf is a superuser who DOES NOT always need to be specified in the LDAP directory (some apps look for it, some apps just use the values you provide and OpenLDAP binds to the super-user defined there) My first suggestion is to (optionally, preferred) remove the database files, since it may not have added correctly, edit test1.ldif and remove the user (last 3 lines), and readd. If it still crashes, consider limiting the options on the server and recompiling pretty vanilla. Some ideas, no firm reason. ktrace ldapadd to find details. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FBSD 7.1-STABLE: pkg_delete: segmentation fault
Hello Everybody, Since several days ago I get a segmentation fault on a FreeBSD 7.1-STABLE/AMD64 box when invoking 'pkg_delete' on installed packages to delete them. This box has been most recently 'built-world' and I did a 'make delete-files' and sibblings as a precaution - but I still get this error. I suspect a DB47 issue (if this is possoble, but I don't know). How can the database be repaired without loosing informations about the installed packages and is this shown degmentation-fault issue a well known issue? Thanks in advance, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Nagios-3.0.6 [Segmentation fault]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Isaac Mabapa said the following on 30.01.2009 12:04: Hi I'm having a problem with trying to start nagios-3.0.6 with embedded perl. I'm running freebsd 7.1-RELEASE-p2 with perl-5.8.9. when i try to start nagios i get this error. Performing sanity check of nagios configuration: OK Starting nagios. Segmentation fault is this this a known bug ? Hi. This bug was recently discussed in freebsd-ports. http://www.freebsd.org/cgi/getmsg.cgi?fetch=524413+527152+/usr/local/www/db/text/2009/freebsd-ports/20090125.freebsd-ports - -- Regards, Bogdan Potishuk - --- KeyID: 0x84B8D5142569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B Keyserver: keyserver.pgp.com - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkmEPgoACgkQhLjVFCVp0wtrvgCg+d5AQVPVgUjTqSafQCYgFpWt AjMAn0abbBgUzpMmCvXyNu7JbLglLKLC =1RTw -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Nagios-3.0.6 [Segmentation fault]
Hi I'm having a problem with trying to start nagios-3.0.6 with embedded perl. I'm running freebsd 7.1-RELEASE-p2 with perl-5.8.9. when i try to start nagios i get this error. Performing sanity check of nagios configuration: OK Starting nagios. Segmentation fault is this this a known bug ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
PHP 5.2.8 crash (segmentation fault 11)
Hi all:
Freshly compiled PHP 5.2.8 with PECL and PHP5-extensions support
on FreeBSD 7.1 (i386) seems to be crashing in
#0 0x28e3e006 in hash_lookup (hashtab=0x29ea2f70,
key=0xbfbfea30 \221??\222)??{\206)p/??)??\r\226)`Qp() at misc.c:349
349 for (ret = hashtab-table[hash_index (hashtab,key)]; ret; ret =
ret-next)
[New Thread 0x28759400 (LWP 100083)]
The stack frame are shown below.
(gdb) bt
#0 0x28e3e006 in hash_lookup (hashtab=0x29ea2f70,
key=0xbfbfea30 \221??\222)??{\206)p/??)??\r\226)`Qp() at misc.c:349
#1 0x29867dae in find_alias () from /usr/local/lib/librecode.so.3
#2 0x29869361 in recode_new_outer () from /usr/local/lib/librecode.so.3
#3 0x2981dd6e in zm_startup_recode ()
from /usr/local/lib/php/20060613-debug/recode.so
#4 0x081c0f65 in zend_startup_module_ex (module=0x287cd100)
at /usr/ports/lang/php5/work/php-5.2.8/Zend/zend_API.c:1472
#5 0x081c81d2 in zend_hash_apply (ht=0x82f0a80,
apply_func=0x81c0dc0 zend_startup_module_ex)
at /usr/ports/lang/php5/work/php-5.2.8/Zend/zend_hash.c:673
#6 0x081c112f in zend_startup_modules ()
at /usr/ports/lang/php5/work/php-5.2.8/Zend/zend_API.c:1519
#7 0x08166db8 in php_module_startup (sf=0x82ec200, additional_modules=0x0,
num_additional_modules=0)
at /usr/ports/lang/php5/work/php-5.2.8/main/main.c:1843
#8 0x0823abf1 in php_cli_startup (sapi_module=0x82ec200)
at /usr/ports/lang/php5/work/php-5.2.8/sapi/cli/php_cli.c:357
#9 0x0823b8a6 in main (argc=2, argv=0xbfbfeda8)
at /usr/ports/lang/php5/work/php-5.2.8/sapi/cli/php_cli.c:716
Anybody pointers as to how to solve this issue ?
thanks
Saifi.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PHP 5.2.8 crash (segmentation fault 11)
Saifi Khan wrote:
Hi all:
Freshly compiled PHP 5.2.8 with PECL and PHP5-extensions support
on FreeBSD 7.1 (i386) seems to be crashing in
#0 0x28e3e006 in hash_lookup (hashtab=0x29ea2f70,
key=0xbfbfea30 \221Û\222)À{\206)p/ê)ì\r\226)`Qp() at misc.c:349
349 for (ret = hashtab-table[hash_index (hashtab,key)]; ret; ret =
ret-next)
[New Thread 0x28759400 (LWP 100083)]
The stack frame are shown below.
snip
Anybody pointers as to how to solve this issue ?
Isn't this simply the classic problem with the order of the extensions
in extensions.ini?
http://www.pingle.org/2006/10
/Morgan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /usr/ports/databases/dbf segmentation fault
| Y | 210 | 8 | 4 | | CSUPPLIERB | C | 218 | 10 | 0 | | CSUPPLIER2 | C | 222 | 11 | 0 | |NDISCDAYS | N | 22d | 2 | 0 | | NDISCPCENT | N | 22f | 7 | 4 | |CBANKNAME | C | 236 | 35 | 0 | | CBRANCHBSB | C | 259 | 18 | 0 | |CCARDTYPE | C | 26b | 17 | 0 | | CCARDNO | C | 27c | 19 | 0 | | CCARDEXPIR | C | 28f | 4 | 0 | | CCARDHOLDE | C | 293 | 35 | 0 | | CUSER1 | C | 2b6 | 20 | 0 | | CUSER2 | C | 2ca | 20 | 0 | | CUSER3 | C | 2de | 20 | 0 | | CKEYLIST_I | C | 2f2 | 8 | 0 | | MNOTES | M | 2fa | 4 | 0 | | ADDEDBY | C | 2fe | 3 | 0 | |MWATCHOUT | M | 301 | 4 | 0 | | DCREATED | D | 305 | 8 | 0 | | LCUSTTAXIN | L | 30d | 1 | 0 | | LUSEPARENT | L | 30e | 1 | 0 | | CCONTACTIF | C | 30f | 4 | 0 | | CCREDTAXCO | C | 313 | 3 | 0 | | CCREDCACC_ | C | 316 | 10 | 0 | | LPAYDIRECT | L | 320 | 1 | 0 | | CSUPPLIERT | C | 321 | 15 | 0 | |CDEFLOCID | C | 330 | 3 | 0 | | LOCREQUIRE | L | 333 | 1 | 0 | |CRM_CY_ID | C | 334 | 10 | 0 | | CRM_CONTAC | C | 33e | 10 | 0 | | CUSER4 | C | 348 | 20 | 0 | | BPAYCODE | C | 35c | 9 | 0 | | IBACKORDER | I | 365 | 4 | 0 | | LPRINTBACK | L | 369 | 1 | 0 | | fps_data.d | b | 63 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | +---+---+---+--- +---+ ...could the reported date be a problem??? stat cardfile.dbf 97 918810 -rwxrwxrwx 1 tom tom 3704992 549139 Jan 10 11:22:17 2009 Jan 9 18:32:14 2009 Jan 10 10:00:05 2009 Jan 9 18:32:13 2009 4096 1120 0 cardfile.dbf ...so I don't think I can change the date...seems like the reported date is a separate date within the dbf file format??? THE COMMAND... dbf --csv ~/cardfile.csv ~/cardfile.dbf dBase Reader and Converter V. 0.8.3.1, (c) 2002 - 2004 by Bjoern Berg Export from /home/tom/cardfile.dbf to /home/tom/cardfile.csv Segmentation fault (core dumped) ls -l cardfile* -rw-r--r-- 1 tom tom 1032192 Jan 10 10:21 cardfile.csv -rwxrwxrwx 1 tom tom 549139 Jan 9 18:32 cardfile.dbf ...tried this as root - same result sig 11... ...tried this using cardfile1.csv as output file - same result sig 11 ... ...the file created is a csv format file with just the column headers from the dbf and part of the first record dmesg pid 7005 (dbf), uid 1001: exited on signal 11 (core dumped) I have a dump file dbf.core if this helps but I thought I shouldn't post it because it is an address file with at least one record containing private contact info of one of my colleagues. Cheers, Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
/usr/ports/databases/dbf segmentation fault
| |CBANKNAME | C | 236 | 35 | 0 | | CBRANCHBSB | C | 259 | 18 | 0 | |CCARDTYPE | C | 26b | 17 | 0 | | CCARDNO | C | 27c | 19 | 0 | | CCARDEXPIR | C | 28f | 4 | 0 | | CCARDHOLDE | C | 293 | 35 | 0 | | CUSER1 | C | 2b6 | 20 | 0 | | CUSER2 | C | 2ca | 20 | 0 | | CUSER3 | C | 2de | 20 | 0 | | CKEYLIST_I | C | 2f2 | 8 | 0 | | MNOTES | M | 2fa | 4 | 0 | | ADDEDBY | C | 2fe | 3 | 0 | |MWATCHOUT | M | 301 | 4 | 0 | | DCREATED | D | 305 | 8 | 0 | | LCUSTTAXIN | L | 30d | 1 | 0 | | LUSEPARENT | L | 30e | 1 | 0 | | CCONTACTIF | C | 30f | 4 | 0 | | CCREDTAXCO | C | 313 | 3 | 0 | | CCREDCACC_ | C | 316 | 10 | 0 | | LPAYDIRECT | L | 320 | 1 | 0 | | CSUPPLIERT | C | 321 | 15 | 0 | |CDEFLOCID | C | 330 | 3 | 0 | | LOCREQUIRE | L | 333 | 1 | 0 | |CRM_CY_ID | C | 334 | 10 | 0 | | CRM_CONTAC | C | 33e | 10 | 0 | | CUSER4 | C | 348 | 20 | 0 | | BPAYCODE | C | 35c | 9 | 0 | | IBACKORDER | I | 365 | 4 | 0 | | LPRINTBACK | L | 369 | 1 | 0 | | fps_data.d | b | 63 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | | | |0 | 0 | 0 | +---+---+---+--- +---+ ...could the reported date be a problem??? stat cardfile.dbf 97 918810 -rwxrwxrwx 1 tom tom 3704992 549139 Jan 10 11:22:17 2009 Jan 9 18:32:14 2009 Jan 10 10:00:05 2009 Jan 9 18:32:13 2009 4096 1120 0 cardfile.dbf ...so I don't think I can change the date...seems like the reported date is a separate date within the dbf file format??? THE COMMAND... dbf --csv ~/cardfile.csv ~/cardfile.dbf dBase Reader and Converter V. 0.8.3.1, (c) 2002 - 2004 by Bjoern Berg Export from /home/tom/cardfile.dbf to /home/tom/cardfile.csv Segmentation fault (core dumped) ls -l cardfile* -rw-r--r-- 1 tom tom 1032192 Jan 10 10:21 cardfile.csv -rwxrwxrwx 1 tom tom 549139 Jan 9 18:32 cardfile.dbf ...tried this as root - same result sig 11... ...tried this using cardfile1.csv as output file - same result sig 11 ... ...the file created is a csv format file with just the column headers from the dbf and part of the first record dmesg pid 7005 (dbf), uid 1001: exited on signal 11 (core dumped) I have a dump file dbf.core if this helps but I thought I shouldn't post it because it is an address file with at least one record containing private contact info of one of my colleagues. Cheers, Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault (core dumped)
On Sun, 23 Nov 2008 21:33:47 +
Marwan Sultan [EMAIL PROTECTED] wrote:
Hello Jerry,
Its easy to fix, as they advised.
Check the file file extensions.ini which is
in /usr/local/etc/php/extensions.ini
You will see your php modules, for some reasons the loading order of
PHP modules it needs to be changed .. You can do the follow..and its
for bignners..but saves you the headech.
Comment first line with - #
save and exitnow see the output of php -v
if the error exist (which will for the first 10 lines maybe)
repeat again for next line..and same untill you see no error of the
php -v
When you findout the modulethat cusing your problem...move it to the
top of the list of modules (top of the file) save and exit...and your
done.. please write for me back which module in your case cused the
problem.
Out of experince.. SHMOP, READLINE, RECODE, SOAP, SNMP could cuuse
your problem
The first problem was easy to fix, I just rebuilt sqlite.so
{databases/php-sqlite}; however, PHP still crashed. I discovered
through trial and error that the problem was with pspell.so. I
rebuilt that port but the problem continued. I then rebuilt 'aspell'
and then rebuilt the 'pspell' port and the problem disappeared.
I wasted several hours getting to the bottom of this problem. There
must be a better way.
By the way, I though that ';' was the symbol to use to comment out a
line in extensions.ini rather than '#'.
--
Jerry
[EMAIL PROTECTED]
In Christianity, a man may have only one wife.
This is called Monotony.
signature.asc
Description: PGP signature
Re: Segmentation fault (core dumped)
On Sat, 22 Nov 2008 22:52:07 + Marwan Sultan [EMAIL PROTECTED] wrote: I think I know what you are talking about.. What is the output of the command php -v ? any errors? I have been have a similar problem lately. ~ $ php -v PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20060613/sqlite.so' - /usr/local/lib/php/20060613/sqlite.so: Undefined symbol spl_ce_Countable in Unknown on line 0 PHP 5.2.6 with Suhosin-Patch 0.9.6.2 (cli) (built: Nov 21 2008 20:45:19) Copyright (c) 1997-2008 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies Segmentation fault: 11 (core dumped) I have been trying to correct it without results. -- Jerry [EMAIL PROTECTED] Your lover will never wish to leave you. signature.asc Description: PGP signature
Re: Segmentation fault (core dumped)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 tethys ocean wrote: Hi to all The server is give this error whenever i want to start apache22. why? Most expected reason - PHP modules. Try to comment modules in /usr/local/etc/php/extensions.ini with ; and check results by php -v or php -i in shell. - -- Regards, Bogdan Potishuk - --- KeyID: 0x84B8D5142569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B Keyserver: keyserver.pgp.com - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkkpV6EACgkQhLjVFCVp0wuBTgCffJxoUELOPuBzszCHOZ4r0nu6 CqwAoLvQB2pRvqqkqAhjJDVJYijdNk6S =QF0q -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (core dumped)
Hi again İ found out what problem is. users had changed some libs of python and apache. After reinstall apache phyton and mod_python it works. so so thanks. regards. On Sat, Nov 22, 2008 at 9:23 PM, tethys ocean [EMAIL PROTECTED]wrote: Hi to all The server is give this error whenever i want to start apache22. why? regards -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Segmentation fault (core dumped)
Hello Jerry, Its easy to fix, as they advised. Check the file file extensions.ini which is in /usr/local/etc/php/extensions.ini You will see your php modules, for some reasons the loading order of PHP modules it needs to be changed .. You can do the follow..and its for bignners..but saves you the headech. Comment first line with - # save and exitnow see the output of php -v if the error exist (which will for the first 10 lines maybe) repeat again for next line..and same untill you see no error of the php -v When you findout the modulethat cusing your problem...move it to the top of the list of modules (top of the file) save and exit...and your done.. please write for me back which module in your case cused the problem. Out of experince.. SHMOP, READLINE, RECODE, SOAP, SNMP could cuuse your problem Thank you. Marwan SUltan.PP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20060613/sqlite.so' - /usr/local/lib/php/20060613/sqlite.so: Undefined symbol spl_ce_Countable in Unknown on line 0 PHP 5.2.6 with Suhosin-Patch 0.9.6.2 (cli) (built: Nov 21 2008 20:45:19) Copyright (c) 1997-2008 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies Segmentation fault: 11 (core dumped) I have been trying to correct it without results. -- Jerry [EMAIL PROTECTED] Your lover will never wish to leave you. _ Windows Live Hotmail now works up to 70% faster. http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_faster_112008___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Segmentation fault (core dumped)
Hi to all The server is give this error whenever i want to start apache22. why? regards -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (core dumped)
tethys ocean wrote:
Hi to all
The server is give this error whenever i want to start apache22. why?
regards
Because something's wrong.
Cheers,
Matthew
What? Not enough of an answer? It's all the answer anyone can give
considering the parcity of information you supply in your question.
To debug this properly could require any or all of:
* your httpd.conf
* the output of
ldd /usr/local/sbin/httpd
* a traceback from httpd.core, although this won't be much use unless
you've compiled httpd with debug symbols.
* the result of running:
truss -f /usr/local/sbin/httpd {+ any other arguments you usually use}
* If you're using mod_php, then the contents of
/usr/local/etc/php/extensions.ini
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: Segmentation fault (core dumped)
I have no idea since any other people doing something but i dont know exactly according to their claim he doing some stuff with python for web and i suppose he want to restart apache python perl etc all packet is installed. On Sat, Nov 22, 2008 at 9:36 PM, Kevin Kinsey [EMAIL PROTECTED] wrote: tethys ocean wrote: Hi to all The server is give this error whenever i want to start apache22. why? regards Well, there could be any number of reasons why this happens. In my experience, it's because you have Apache loading a broken or incompatible module. Have you recently rebuilt Apache, or some other module (like Perl, PHP, Python) that is used by Apache? Kevin Kinsey -- If it ain't baroque, don't fix it. ---P.D.Q. Bach -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (core dumped)
tethys ocean wrote: Hi to all The server is give this error whenever i want to start apache22. why? regards Well, there could be any number of reasons why this happens. In my experience, it's because you have Apache loading a broken or incompatible module. Have you recently rebuilt Apache, or some other module (like Perl, PHP, Python) that is used by Apache? Kevin Kinsey -- If it ain't baroque, don't fix it. ---P.D.Q. Bach ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (core dumped)
apache-2.2.9_5 = up-to-date with port
autoconf-2.62 = up-to-date with port
db41-4.1.25_4 = up-to-date with port
gd-2.0.35,1 = up-to-date with port
gdbm-1.8.3_3= up-to-date with port
irc-2.11.2p1= up-to-date with port
ircii-20060725_1= up-to-date with port
nano-2.0.9 = up-to-date with port
p5-HTML-Template-2.9_1 = up-to-date with port
portupgrade-2.4.6,2 = up-to-date with port
py25-MySQLdb-1.2.2 = up-to-date with port
py25-bsddb-2.5.2_2 = up-to-date with port
py25-django-1.0.1 = up-to-date with port
py25-flup-1.0.1 = up-to-date with port
py25-gdbm-2.5.2 = up-to-date with port
python25-2.5.2_3= up-to-date with port
rsync-3.0.4 = up-to-date with port
ruby-1.8.6.287,1= up-to-date with port
ruby18-bdb-0.6.4= up-to-date with port
tcl-8.4.19,1= up-to-date with port
unzip-5.52_5= up-to-date with port
webalizer-2.20.1_2 = up-to-date with port
On Sat, Nov 22, 2008 at 9:39 PM, Matthew Seaman
[EMAIL PROTECTED] wrote:
tethys ocean wrote:
Hi to all
The server is give this error whenever i want to start apache22. why?
regards
Because something's wrong.
Cheers,
Matthew
What? Not enough of an answer? It's all the answer anyone can give
considering the parcity of information you supply in your question.
To debug this properly could require any or all of:
* your httpd.conf
* the output of
ldd /usr/local/sbin/httpd
/usr/local/sbin/httpd:
libm.so.4 = /lib/libm.so.4 (0x280c7000)
libaprutil-1.so.3 = /usr/local/lib/libaprutil-1.so.3 (0x280dd000)
libdb41.so.1 = /usr/local/lib/libdb41.so.1 (0x280f7000)
libexpat.so.6 = /usr/local/lib/libexpat.so.6 (0x28194000)
libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x281b2000)
libapr-1.so.3 = /usr/local/lib/libapr-1.so.3 (0x2829f000)
libcrypt.so.3 = /lib/libcrypt.so.3 (0x282c1000)
libpthread.so.2 = /lib/libpthread.so.2 (0x282d9000)
libc.so.6 = /lib/libc.so.6 (0x282fe000)
* a traceback from httpd.core, although this won't be much use unless
you've compiled httpd with debug symbols.
locate httpd.core
/usr/local/etc/rc.d/httpd.core
/usr/ports/distfiles/tmp/lib/httpd.core
* the result of running:
truss -f /usr/local/sbin/httpd {+ any other arguments you usually
use}
truss -f /usr/local/sbin/httpd
truss: cannot open /proc/curproc/mem: No such file or directory
truss: cannot open1 /proc/61323/mem: No such file or directory
* If you're using mod_php, then the contents of
/usr/local/etc/php/extensions.ini
extension=bcmath.so
extension=bz2.so
extension=calendar.so
extension=ctype.so
extension=curl.so
extension=pcre.so
extension=simplexml.so
extension=spl.so
extension=dom.so
extension=filter.so
extension=gd.so
extension=gettext.so
extension=hash.so
extension=iconv.so
extension=json.so
extension=mbstring.so
extension=mcrypt.so
extension=mysql.so
extension=pdo.so
extension=pdo_sqlite.so
extension=posix.so
extension=session.so
extension=sockets.so
extension=sqlite.so
extension=tokenizer.so
extension=xml.so
extension=xmlreader.so
extension=xmlwriter.so
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--
Share now a pigeon's flight
Bluebound along the ancient skies,
Its women forever hair and mammal,
A Mediterranean town may arise
If you rip apart a pigeon's heart.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (core dumped)
On Sat, 22 Nov 2008 21:53:02 +0200, tethys ocean [EMAIL PROTECTED] wrote: I have no idea since any other people doing something but i dont know exactly according to their claim he doing some stuff with python for web and i suppose he want to restart apache Maybe it's a good idea to avoid messing up with this particular Apache instance then. If you don't know how it has been installed, and you cannot find out, and you are only guessing that a restart should fix things, then don't do that... Geez :P ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (core dumped)
i found something from bash_hist. he deinstall all pkg. (apache php and python) while he is upgrade. i ve reinstall apache22 and port upgraded. than now i will reinstall all deinstalled package and fix it On Sat, Nov 22, 2008 at 10:12 PM, Giorgos Keramidas [EMAIL PROTECTED] wrote: On Sat, 22 Nov 2008 21:53:02 +0200, tethys ocean [EMAIL PROTECTED] wrote: I have no idea since any other people doing something but i dont know exactly according to their claim he doing some stuff with python for web and i suppose he want to restart apache Maybe it's a good idea to avoid messing up with this particular Apache instance then. If you don't know how it has been installed, and you cannot find out, and you are only guessing that a restart should fix things, then don't do that... Geez :P -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (core dumped)
The server is give this error whenever i want to start apache22. why? regards no idea,but most probably you use PHP and added lots of it's modules, some of them crashes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Segmentation fault (core dumped)
Hi.. I think I know what you are talking about.. What is the output of the command php -v ? any errors? Marwan Date: Sat, 22 Nov 2008 21:23:24 +0200 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] CC: Subject: Segmentation fault (core dumped) Hi to all The server is give this error whenever i want to start apache22. why? regards-- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] _ Get more done, have more fun, and stay more connected with Windows Mobile®. http://clk.atdmt.com/MRT/go/119642556/direct/01/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: Suhosin Segmentation Fault]
Not much return on freebsd-isp. I try again here on freebsd-questions. Original-Nachricht Betreff: Suhosin Segmentation Fault Datum: Mon, 13 Oct 2008 09:49:09 +0200 Von: Alain Wolf [EMAIL PROTECTED] An: [EMAIL PROTECTED] Newsgruppen: gmane.os.freebsd.isp After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all websites just display a blank page and every HTTP request created a line as follows in the logs: child pid 80326 exit signal Segmentation fault (11) This same problem happened on another server a few months ago after the upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports all went back to normal. However several rebuilds of all ports did not solve the problem on this one. To narrow down the problem: After disabling the PHP module in Apache the problem disappears. Re-enabling PHP, but disabling the Suhosin extension also works fine. The trick found in this forum, to load the Suhosin extension before all other PHP extensions in /usr/local/etc/php/extensions.ini does not help. In fact not loading any extension at all except Suhosin creates the segfault errors. Commenting out our Suhosin settings in php.ini to load it with default values did not help. FreeBSD 6.3-RELEASE-p5 Apache 2.2.9 (DAV/2 mod_python/3.3.1 Python/2.5.2 SVN/1.5.2) PHP Version 5.2.6 Suhosin Patch 0.9.6.2 Suhosin PHP extension 0.9.27 All installed from the ports. PHP (cli) seems to run fine at all times when called from the command-line. Any suggestions? Thanks Alain Wolf, Zurich, Switzerland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote: Not much return on freebsd-isp. I try again here on freebsd-questions. Original-Nachricht Betreff: Suhosin Segmentation Fault Datum: Mon, 13 Oct 2008 09:49:09 +0200 Von: Alain Wolf [EMAIL PROTECTED] An: [EMAIL PROTECTED] Newsgruppen: gmane.os.freebsd.isp After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all websites just display a blank page and every HTTP request created a line as follows in the logs: child pid 80326 exit signal Segmentation fault (11) This same problem happened on another server a few months ago after the upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports all went back to normal. However several rebuilds of all ports did not solve the problem on this one. To narrow down the problem: After disabling the PHP module in Apache the problem disappears. Re-enabling PHP, but disabling the Suhosin extension also works fine. The trick found in this forum, to load the Suhosin extension before all other PHP extensions in /usr/local/etc/php/extensions.ini does not help. In fact not loading any extension at all except Suhosin creates the segfault errors. Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. The extension ordering problem, however, has been thoroughly discussed on -ports in the past. It happens to some and not others. There is no guaranteed way to determine what works and what doesn't. You have to literally enable line-by-line until you figure out which one is causing the problem. You can also try building lang/php5 with DEBUG enabled and then when PHP segfaults, run gdb on the coredump and see if you can get a coherent backtrace (sometimes difficult with Apache in the way) to see what sort of functions are causing the crash; often each extension has its own function names, so that might give you some clues. PHP (cli) seems to run fine at all times when called from the command-line. Now that's very interesting, given as the CLI version also loads all the extensions listed in extensions.ini. Can you post your /usr/local/etc/php/extensions.ini? You didn't list off what extensions you have installed. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: Suhosin Segmentation Fault]
Jeremy Chadwick wrote: Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. % grep suhosin /usr/local/etc/php/extensions.ini extension=suhosin.so It's both a set of patches to the PHP core, and a loadable module. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote: Jeremy Chadwick wrote: Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. % grep suhosin /usr/local/etc/php/extensions.ini extension=suhosin.so It's both a set of patches to the PHP core, and a loadable module. Cheers, Matthew Are you sure? # find /usr/local/lib/php -name *suhosin* -ls # # grep -i suhosin /var/db/ports/php5/options WITH_SUHOSIN=true # grep -i suhosin /usr/local/etc/php/extensions.ini # # pkg_version -v | grep php5 php5-5.2.6_2= up-to-date with port php5-extensions-1.1 = up-to-date with port php5-mysql-5.2.6_2 = up-to-date with port php5-pcre-5.2.6_2 = up-to-date with port php5-simplexml-5.2.6_2 = up-to-date with port # grep -i php5 /usr/local/etc/apache22/httpd.conf LoadModule php5_modulelibexec/apache22/libphp5.so # php -i | grep -i suhosin This server is protected with the Suhosin Patch 0.9.6.2 suhosin.log.phpscript = 0 = 0 suhosin.log.phpscript.is_safe = Off = Off suhosin.log.phpscript.name = no value = no value suhosin.log.sapi = no value = no value suhosin.log.script = no value = no value suhosin.log.script.name = no value = no value suhosin.log.syslog = no value = no value suhosin.log.syslog.facility = no value = no value suhosin.log.syslog.priority = no value = no value suhosin.log.use-x-forwarded-for = Off = Off :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 2:35 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote: Jeremy Chadwick wrote: Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. % grep suhosin /usr/local/etc/php/extensions.ini extension=suhosin.so It's both a set of patches to the PHP core, and a loadable module. Cheers, Matthew Are you sure? Yes - the suhosin extension is located in the ports tree at: /usr/ports/security/php-suhosin Install instructions are at: http://www.hardened-php.net/suhosin/how_to_install_or_upgrade.html#installing_the_extension It's been a while since I've looked at the suhosin options and I can't remember what the differences are between the extension and the core-php patch. Matt # find /usr/local/lib/php -name *suhosin* -ls # # grep -i suhosin /var/db/ports/php5/options WITH_SUHOSIN=true # grep -i suhosin /usr/local/etc/php/extensions.ini # # pkg_version -v | grep php5 php5-5.2.6_2= up-to-date with port php5-extensions-1.1 = up-to-date with port php5-mysql-5.2.6_2 = up-to-date with port php5-pcre-5.2.6_2 = up-to-date with port php5-simplexml-5.2.6_2 = up-to-date with port # grep -i php5 /usr/local/etc/apache22/httpd.conf LoadModule php5_modulelibexec/apache22/libphp5.so # php -i | grep -i suhosin This server is protected with the Suhosin Patch 0.9.6.2 suhosin.log.phpscript = 0 = 0 suhosin.log.phpscript.is_safe = Off = Off suhosin.log.phpscript.name = no value = no value suhosin.log.sapi = no value = no value suhosin.log.script = no value = no value suhosin.log.script.name = no value = no value suhosin.log.syslog = no value = no value suhosin.log.syslog.facility = no value = no value suhosin.log.syslog.priority = no value = no value suhosin.log.use-x-forwarded-for = Off = Off :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: Suhosin Segmentation Fault]
Hi, all-- On Oct 15, 2008, at 12:47 PM, Matt wrote: It's been a while since I've looked at the suhosin options and I can't remember what the differences are between the extension and the core-php patch. If you check the following, they discuss the difference in protection between using just the patch versus the extension: http://www.hardened-php.net/suhosin/why.html http://www.hardened-php.net/suhosin/a_feature_list.html Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: Suhosin Segmentation Fault]
On 15.10.2008 20:55, Jeremy Chadwick wrote: On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote: Not much return on freebsd-isp. I try again here on freebsd-questions. Original-Nachricht Betreff: Suhosin Segmentation Fault Datum: Mon, 13 Oct 2008 09:49:09 +0200 Von: Alain Wolf [EMAIL PROTECTED] An: [EMAIL PROTECTED] Newsgruppen: gmane.os.freebsd.isp After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all websites just display a blank page and every HTTP request created a line as follows in the logs: child pid 80326 exit signal Segmentation fault (11) This same problem happened on another server a few months ago after the upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports all went back to normal. However several rebuilds of all ports did not solve the problem on this one. To narrow down the problem: After disabling the PHP module in Apache the problem disappears. Re-enabling PHP, but disabling the Suhosin extension also works fine. The trick found in this forum, to load the Suhosin extension before all other PHP extensions in /usr/local/etc/php/extensions.ini does not help. In fact not loading any extension at all except Suhosin creates the segfault errors. Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. Suhosin is *both*. A patch for php and a extension module for PHP. From http://www.hardened-php.net/suhosin/index.html: Suhosin comes in two independent parts, that can be used separately or in combination. The first part is a small patch against the PHP core, that implements a few low-level protections against bufferoverflows or format string vulnerabilities and the second part is a powerful PHP extension that implements all the other protections. The suhosin patch works fine on our servers. But the extension does not. The extension ordering problem, however, has been thoroughly discussed on -ports in the past. It happens to some and not others. There is no guaranteed way to determine what works and what doesn't. You have to literally enable line-by-line until you figure out which one is causing the problem. I tried enabling and disabling extensions. All of them work, as long as suhosin.so is not loaded. Regardless of the order. If I disable all other extensions and load only suhosin.so in /usr/local/etc/php/extensions.ini the apache processes are still crashing. You can also try building lang/php5 with DEBUG enabled and then when PHP segfaults, run gdb on the coredump and see if you can get a coherent backtrace (sometimes difficult with Apache in the way) to see what sort of functions are causing the crash; often each extension has its own function names, so that might give you some clues. Hard for me, as this disrupts customer services. We are running without the extensions for now. PHP (cli) seems to run fine at all times when called from the command-line. Now that's very interesting, given as the CLI version also loads all the extensions listed in extensions.ini. Can you post your /usr/local/etc/php/extensions.ini? You didn't list off what extensions you have installed. cat /usr/local/etc/php/extensions.ini extension=gd.so extension=ctype.so extension=pcre.so extension=session.so extension=bz2.so extension=openssl.so extension=zlib.so extension=mbstring.so extension=mysql.so extension=pdf.so extension=mcrypt.so extension=simplexml.so extension=spl.so extension=mysqli.so extension=xml.so extension=iconv.so extension=hash.so extension=tokenizer.so extension=calendar.so extension=ftp.so extension=xmlrpc.so extension=xmlwriter.so extension=zip.so extension=filter.so ;extension=suhosin.so extension=wddx.so extension=mhash.so extension=json.so extension=dom.so extension=xmlreader.so extension=exif.so extension=ncurses.so extension=gettext.so extension=ldap.so extension=pdo.so extension=soap.so extension=tidy.so extension=pdo_sqlite.so extension=apc.so extension=readline.so extension=xsl.so extension=curl.so ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 02:47:00PM -0500, Matt wrote: On Wed, Oct 15, 2008 at 2:35 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote: Jeremy Chadwick wrote: Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. % grep suhosin /usr/local/etc/php/extensions.ini extension=suhosin.so It's both a set of patches to the PHP core, and a loadable module. Cheers, Matthew Are you sure? Yes - the suhosin extension is located in the ports tree at: /usr/ports/security/php-suhosin Install instructions are at: http://www.hardened-php.net/suhosin/how_to_install_or_upgrade.html#installing_the_extension It's been a while since I've looked at the suhosin options and I can't remember what the differences are between the extension and the core-php patch. Deep within their forums, I found an answer in a thread. The thread pointed me to this: http://www.hardened-php.net/suhosin/a_feature_list.html Engine Protection is not available in security/php-suhosin. Seems to me that the benefits of using the patch version easily outweigh that of the extension version, solely for protection against formatted string vulnerabilities. I also found this amusing tidbit, which is a sticky post on their forum: http://forum.hardened-php.net/viewtopic.php?id=122 That sticky also states that pspell.so will cause Suhosin to crash, advocating that pspell.so must come last in extension.so, but then also advocates simply not using pspell at all. I'm sure that does nothing but confuse users. Seems the OP has also posted there: http://forum.hardened-php.net/viewtopic.php?id=501 It would be interesting to know if the segfaults people experience are specific to the extension version of Suhosin. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: Suhosin Segmentation Fault]
On Wed, Oct 15, 2008 at 10:01:13PM +0200, Alain Wolf wrote: On 15.10.2008 20:55, Jeremy Chadwick wrote: On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote: Not much return on freebsd-isp. I try again here on freebsd-questions. Original-Nachricht Betreff: Suhosin Segmentation Fault Datum: Mon, 13 Oct 2008 09:49:09 +0200 Von: Alain Wolf [EMAIL PROTECTED] An: [EMAIL PROTECTED] Newsgruppen: gmane.os.freebsd.isp After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all websites just display a blank page and every HTTP request created a line as follows in the logs: child pid 80326 exit signal Segmentation fault (11) This same problem happened on another server a few months ago after the upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports all went back to normal. However several rebuilds of all ports did not solve the problem on this one. To narrow down the problem: After disabling the PHP module in Apache the problem disappears. Re-enabling PHP, but disabling the Suhosin extension also works fine. The trick found in this forum, to load the Suhosin extension before all other PHP extensions in /usr/local/etc/php/extensions.ini does not help. In fact not loading any extension at all except Suhosin creates the segfault errors. Suhosin is not an extension you load in extensions.ini; it's a patch applied to the core of PHP. Suhosin is *both*. A patch for php and a extension module for PHP. From http://www.hardened-php.net/suhosin/index.html: Suhosin comes in two independent parts, that can be used separately or in combination. The first part is a small patch against the PHP core, that implements a few low-level protections against bufferoverflows or format string vulnerabilities and the second part is a powerful PHP extension that implements all the other protections. Except their own website contradicts themselves in many other places, including on their forums *and* in other documentation. I can refer you to some documentation of theirs that states Suhosin extension sometimes causes other extensions to crash because they try to access internal variables wrongly. You are supposed to use one or the other: the patch, or the extension. You've probably read my other mail by now, so you know that I advocate use of the patch. The suhosin patch works fine on our servers. But the extension does not. So disable it and use only the patch -- problem solved. I'm CC'ing ale@ on this thread, because he's probably not on -questions, and this has now become a -ports thing. He can comment on what to do about these crashes. I'm of the opinion that security/php-suhosin should be nuked, especially if the patch works fine for everyone but the extension causes problems. The extension ordering problem, however, has been thoroughly discussed on -ports in the past. It happens to some and not others. There is no guaranteed way to determine what works and what doesn't. You have to literally enable line-by-line until you figure out which one is causing the problem. I tried enabling and disabling extensions. All of them work, as long as suhosin.so is not loaded. Regardless of the order. If I disable all other extensions and load only suhosin.so in /usr/local/etc/php/extensions.ini the apache processes are still crashing. You can also try building lang/php5 with DEBUG enabled and then when PHP segfaults, run gdb on the coredump and see if you can get a coherent backtrace (sometimes difficult with Apache in the way) to see what sort of functions are causing the crash; often each extension has its own function names, so that might give you some clues. Hard for me, as this disrupts customer services. We are running without the extensions for now. PHP (cli) seems to run fine at all times when called from the command-line. Now that's very interesting, given as the CLI version also loads all the extensions listed in extensions.ini. Can you post your /usr/local/etc/php/extensions.ini? You didn't list off what extensions you have installed. cat /usr/local/etc/php/extensions.ini extension=gd.so extension=ctype.so extension=pcre.so extension=session.so extension=bz2.so extension=openssl.so extension=zlib.so extension=mbstring.so extension=mysql.so extension=pdf.so extension=mcrypt.so extension=simplexml.so extension=spl.so extension=mysqli.so extension=xml.so extension=iconv.so extension=hash.so extension=tokenizer.so extension=calendar.so extension=ftp.so extension=xmlrpc.so extension=xmlwriter.so extension=zip.so extension=filter.so ;extension=suhosin.so extension=wddx.so extension=mhash.so extension=json.so extension=dom.so extension=xmlreader.so extension=exif.so extension=ncurses.so extension=gettext.so extension=ldap.so extension=pdo.so extension=soap.so extension=tidy.so extension=pdo_sqlite.so
Re: [Fwd: Suhosin Segmentation Fault]
Jeremy Chadwick wrote: You are supposed to use one or the other: the patch, or the extension. Nope, they can be used alone or mixed together (I use both on my servers). For a detailed explanation see: http://www.hardened-php.net/suhosin/why.html I'm CC'ing ale@ on this thread, because he's probably not on -questions, and this has now become a -ports thing. He can comment on what to do about these crashes. Compile PHP in debug and post a backtrace. The suhosin author is a FreeBSD committer, so he can surely help solving the problem. I'm of the opinion that security/php-suhosin should be nuked, especially if the patch works fine for everyone but the extension causes problems. See above. If I disable all other extensions and load only suhosin.so in /usr/local/etc/php/extensions.ini the apache processes are still crashing. Apache version? -- Alex Dupre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
can someone please explain to me what happens to the
allocated memory
called within a function assigned to its local pointer
after this function
ends
Ok - let's see if I get this right:
- the allocated memory
- called within a function
- assigned to a local pointer
Any malloc'ed memory is application global accessible.
Assigning a pointer to
a variable doesn't allocate memory (the compiler and
runtime libraries
already setup storage for the variable, at declaration
time). So, I have no
idea what you mean with the called within a
function part.
--
Mel
thanks for making it even more clear to me.
actually what i meant was this:
void function(void){
char *p;
p = malloc(1);
}
int main(void){
while (1){
function();
/* in the end of this function function()
* the memory is still allocated
* even when the only pointer who knows its address
* does not longer exist
* which is why we have to free() the memory
* during the application runtime
* to avoid it from growing to ridiculous size
*/
}
}
but even if you kill -SEGV `pgrep this` (Segmentation fault (core dumped) the
memory is getting freed anyway (presumably by the glorious kernel). which you
can see dynamicly by typing top in the console.
in other words segmentation fault when free() is not a scary thing here. it is
a matter of style and the way to find own errors. or maybe reading warnings if
you compile with the flags -ansi -pedantic
oh and by the way:
char *
function(void)
{
char buffer[100];
return buffer;
}
that is an easier approach because you get warned on passing an address to a
local variable
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
On Sun, 21 Sep 2008 05:57:06 -0700 (PDT), Nash Nipples [EMAIL PROTECTED]
wrote:
thanks for making it even more clear to me.
actually what i meant was this:
void function(void){
char *p;
p = malloc(1);
}
int main(void){
while (1){
function();
/* in the end of this function function()
* the memory is still allocated
* even when the only pointer who knows its address
* does not longer exist
* which is why we have to free() the memory
* during the application runtime
* to avoid it from growing to ridiculous size
*/
}
}
This won't throw SEGV in free() because, well, it never calls free(),
but it leaks memory like mad :)
but even if you kill -SEGV `pgrep this` (Segmentation fault (core
dumped) the memory is getting freed anyway (presumably by the glorious
kernel). which you can see dynamicly by typing top in the console.
Yes. When a process terminates, the kernel dismantles and releases all
its 'mapped memory areas', including the heap where malloc()'ed memory
comes from.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
On Sunday 21 September 2008 14:57:06 Nash Nipples wrote:
can someone please explain to me what happens to the
allocated memory
called within a function assigned to its local pointer
after this function
ends
Ok - let's see if I get this right:
- the allocated memory
- called within a function
- assigned to a local pointer
Any malloc'ed memory is application global accessible.
Assigning a pointer to
a variable doesn't allocate memory (the compiler and
runtime libraries
already setup storage for the variable, at declaration
time). So, I have no
idea what you mean with the called within a
function part.
--
Mel
thanks for making it even more clear to me.
actually what i meant was this:
void function(void){
char *p;
p = malloc(1);
}
int main(void){
while (1){
function();
/* in the end of this function function()
* the memory is still allocated
* even when the only pointer who knows its address
* does not longer exist
* which is why we have to free() the memory
* during the application runtime
* to avoid it from growing to ridiculous size
*/
}
}
Right, this is one of the annoyances of C-programming Who still knows where
my pointer is. You can use a general rule though:
If I don't return this pointer, and I don't assign this pointer to a
parameter, and I don't assign this pointer to a global variable, I should
free this pointer myself.
(Yes yes, malloc'd static storage - new can of worms).
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
On Sun, 21 Sep 2008 05:57:06 -0700 (PDT)
Nash Nipples [EMAIL PROTECTED] wrote:
but even if you kill -SEGV `pgrep this` (Segmentation fault (core
dumped) the memory is getting freed anyway (presumably by the
glorious kernel). which you can see dynamicly by typing top in the
console.
The idea that malloc() allocates memory is really a C language
abstraction. What it actually does is allocate a region in the
process's virtual address space. The mapping of physical memory to
virtual address space is handled at a lower-level and doesn't rely on
malloc() or free().
in other words segmentation fault when free() is not a scary thing
here. it is a matter of style and the way to find own errors. or
maybe reading warnings if you compile with the flags -ansi -pedantic
I'm not sure what you are saying here, but the handling of dynamic
memory in C is something that needs to be well thought-out in
advance. Bugs is this area can be very difficult and time-consuming
to track-down.
oh and by the way:
char *
function(void)
{
char buffer[100];
return buffer;
}
that is an easier approach because you get warned on passing an
address to a local variable
This was an example of how to generate a failure, it's not an approach.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
On Mon, 22 Sep 2008 02:31:57 +0100, RW [EMAIL PROTECTED] wrote:
Nash Nipples [EMAIL PROTECTED] wrote:
Giorgos Keramidas wrote:
char *
function(void)
{
char buffer[100];
return buffer;
}
that is an easier approach because you get warned on passing an
address to a local variable
This was an example of how to generate a failure, it's not an
approach.
Yes. It was *only* written to illustrate how a particular failure could
happen. I wouldn't recommend this to anyone as a programming approach :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
On Fri, 19 Sep 2008 20:03:03 -0700 (PDT), Unga [EMAIL PROTECTED] wrote: Hi thank you very much for your reply and the test case. That is, in a trivial case like this, free() works well. Hopefully free() works well in all cases too. But my main program is 1900 lines, f1() and f2() are in a 2200 lines second file. The f1() and f2() calls some functions from a 500 lines third file. The main program call another function, f3(), from 2nd file, pass pointers to two functions f4(), f5() of main program. The while loop iterate more than one million times. Its quite a complex situation. You are probably calling free() multiple times for the same buffer. Try tracing the malloc and free calls, using the information from this message: http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179480.html There must be an error somewhere else. I noted free() causes lot of troubles. It is easy to write complex programs if you just let to leak memory. But in my case, since the program iterate millions of times, if I let to leak, I'm sure it will run out of RAM. Leaking memory is *never* a good choice. Especially if you are writing library code that others are supposed to use, or code that is supposed to run millions of times. While it's understandable as a 'quick hack' when you are first writing a program, I've seen far too many 'quick hacks' that lived years and years after the original 'experimental' period passed. Hence the knee-jerk reaction when I see leaks being used as a 'temporary' solution :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
--- On Sat, 9/20/08, Giorgos Keramidas [EMAIL PROTECTED] wrote: From: Giorgos Keramidas [EMAIL PROTECTED] Subject: Re: Segmentation fault when free To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], freebsd-questions@freebsd.org Date: Saturday, September 20, 2008, 2:23 PM On Fri, 19 Sep 2008 20:03:03 -0700 (PDT), Unga [EMAIL PROTECTED] wrote: Hi thank you very much for your reply and the test case. That is, in a trivial case like this, free() works well. Hopefully free() works well in all cases too. But my main program is 1900 lines, f1() and f2() are in a 2200 lines second file. The f1() and f2() calls some functions from a 500 lines third file. The main program call another function, f3(), from 2nd file, pass pointers to two functions f4(), f5() of main program. The while loop iterate more than one million times. Its quite a complex situation. You are probably calling free() multiple times for the same buffer. Try tracing the malloc and free calls, using the information from this message: http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179480.html There must be an error somewhere else. I noted free() causes lot of troubles. It is easy to write complex programs if you just let to leak memory. But in my case, since the program iterate millions of times, if I let to leak, I'm sure it will run out of RAM. Leaking memory is *never* a good choice. Especially if you are writing library code that others are supposed to use, or code that is supposed to run millions of times. While it's understandable as a 'quick hack' when you are first writing a program, I've seen far too many 'quick hacks' that lived years and years after the original 'experimental' period passed. Hence the knee-jerk reaction when I see leaks being used as a 'temporary' solution :) Hi Giorgos, thank you very much for your reply. ktrace.out shows: malloc_init() 0x8103400 = malloc(1024) malloc_init() malloc_init() 0x810b0b0 = malloc(400) : so many malloc : so many free : malloc/free combinations : free(0xbfbfc9c9) 1. This clearly shows my program is trying to free a memory that has not been allocated. How it could have happened? 2. Is it correct to have many malloc_init()? Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
On Sat, 20 Sep 2008 00:31:41 -0700 (PDT), Unga [EMAIL PROTECTED] wrote:
--- On Sat, 9/20/08, Giorgos Keramidas [EMAIL PROTECTED] wrote:
You are probably calling free() multiple times for the same buffer.
Try tracing the malloc and free calls, using the information from
this message:
http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179480.html
Hi Giorgos, thank you very much for your reply.
You are welcome :)
ktrace.out shows:
malloc_init()
0x8103400 = malloc(1024)
malloc_init()
malloc_init()
0x810b0b0 = malloc(400)
:
so many malloc
:
so many free
:
malloc/free combinations
:
free(0xbfbfc9c9)
1. This clearly shows my program is trying to free a memory that has
not been allocated. How it could have happened?
Aha. This looks remarkably like an address in the runtime stack. It
usually happens when you have a function that returns the address of a
'local' variable, instead of a newly allocated heap area, i.e.:
char *
function(void)
{
char buffer[100];
return buf;
}
2. Is it correct to have many malloc_init()?
Yes, that's ok. If your program is threaded, FreeBSD's pthread
implementation calls malloc(3) and malloc_init() takes special care of
initializing the internal malloc state only one time.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
--- On Sat, 9/20/08, Giorgos Keramidas [EMAIL PROTECTED] wrote:
1. This clearly shows my program is trying to free a
memory that has
not been allocated. How it could have happened?
Aha. This looks remarkably like an address in the runtime
stack. It
usually happens when you have a function that returns the
address of a
'local' variable, instead of a newly allocated heap
area, i.e.:
char *
function(void)
{
char buffer[100];
return buf;
}
This problem happens very early stage of my program. Its the very first free()
develops a problem.
I checked again, up to the this problematic free(), functions return newly
allocated strings properly:
char *f( )
{
char *newstr = NULL;
:
newstr = (char *) malloc(p - sp + 1);
if (newstr == NULL)
return NULL;
:
return newstr;
}
Can a yet not executed wrong free() elsewhere cause a problem of this nature?
Best regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
I checked again, up to the this problematic free(),
functions return newly allocated strings properly:
char *f( )
{
char *newstr = NULL;
:
newstr = (char *) malloc(p - sp + 1);
if (newstr == NULL)
return NULL;
:
return newstr;
}
Can a yet not executed wrong free() elsewhere cause a
problem of this nature?
Best regards
Unga
i'm sorry i just dont really cant see a problem with free()
can you please explain it in a more simple way?
it really starts to exceed my screen height
#include stdio.h
#include stdlib.h
#include string.h
char *a;
char *b;
char *c;
char *abd = Hi, im a string
1\0;
char *bbd = Hey, im a string 2\0;
char *f(char *d){
char *newstr = NULL; char *p, *sp;
sp = malloc(strlen (d)); memcpy(sp, d, strlen(d));
p = strchr(sp, 44);
newstr = (char *) malloc(p - sp + 1);
if (newstr == NULL){
newstr = malloc(1);
*newstr = '\0';
return newstr; /* you really dont want to return NULL to strlen() */
}
*p = '\0';
memcpy(newstr, sp, sizeof(char) * (p - sp));
return newstr;
}
char *f1(void){
char *ab;
ab = f(abd);
printf(f1(): %s\n, ab);
return ab;
}
char *f2(void){
char *bb;
bb = f(bbd);
printf(f2(): %s\n, bb);
return bb;
}
int
main(void)
{
while (1)
{
a = f1(); /* malloc and send a string */
b = f2(); /* malloc and send a string */
c =
(char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
printf(main(): %s\n, c);
free(a);
free(b);
free(c);
}
}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
actually what i think someone should really tell you is that maybe you should take a look at the free() manual which is available here http://www.freebsd.org/cgi/man.cgi?query=freeapropos=0sektion=0manpath=FreeBSD+7.0-RELEASEformat=html or you can try to run `man free` in the console. there is a good explanation on diagnostic and debugging malloc related problems can someone please explain to me what happens to the allocated memory called within a function assigned to its local pointer after this function ends ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free [SOLVED]
--- On Sat, 9/20/08, Giorgos Keramidas [EMAIL PROTECTED] wrote:
ktrace.out shows:
malloc_init()
0x8103400 = malloc(1024)
malloc_init()
malloc_init()
0x810b0b0 = malloc(400)
:
so many malloc
:
so many free
:
malloc/free combinations
:
free(0xbfbfc9c9)
1. This clearly shows my program is trying to free a
memory that has
not been allocated. How it could have happened?
Aha. This looks remarkably like an address in the runtime
stack. It
usually happens when you have a function that returns the
address of a
'local' variable, instead of a newly allocated heap
area, i.e.:
char *
function(void)
{
char buffer[100];
return buf;
}
This was indeed the case, worst yet, I was trying to free a part of the buffer
(as per your example above) by mistake which was not allocated by malloc.
Thank you all who helped me.
Best regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
segmentation fault 11
I saw a reference that linux.ko and kqemu.ko can start a segmentation fault 11. My memory is set to 2G in the loader file and physical is 1.77G. Would this cause the problem? _ See how Windows Mobile brings your life together—at home, work, or on the go. http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free [SOLVED]
On Sat, 20 Sep 2008 07:04:03 -0700 (PDT), Unga [EMAIL PROTECTED] wrote:
On Sat, 9/20/08, Giorgos Keramidas [EMAIL PROTECTED] wrote:
: free(0xbfbfc9c9)
1. This clearly shows my program is trying to free a memory that
has not been allocated. How it could have happened?
Aha. This looks remarkably like an address in the runtime stack. It
usually happens when you have a function that returns the address of
a 'local' variable, instead of a newly allocated heap area, i.e.:
char *
function(void)
{
char buffer[100];
return buf;
}
This was indeed the case, worst yet, I was trying to free a part of
the buffer (as per your example above) by mistake which was not
allocated by malloc.
Thank you all who helped me.
Great! You are welcome, of course :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
On Saturday 20 September 2008 13:46:23 Nash Nipples wrote: can someone please explain to me what happens to the allocated memory called within a function assigned to its local pointer after this function ends Ok - let's see if I get this right: - the allocated memory - called within a function - assigned to a local pointer Any malloc'ed memory is application global accessible. Assigning a pointer to a variable doesn't allocate memory (the compiler and runtime libraries already setup storage for the variable, at declaration time). So, I have no idea what you mean with the called within a function part. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Segmentation fault when free
Hi all
I'm running FreeBSD 7 on i386. I have a C program compiled with gcc 4.2.1
20070719.
Logically my program is:
char *a;
char *b;
char *c;
while (cond)
{
a = f1(); /* malloc() and send a string */
b = f2(); /* malloc() and send a string */
c = (char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
free(a);
free(b);
}
When it executes free(b), my program exits with Segmentation fault: 11. The
free(a) executes well.
The problem is with free(b). Even swap free(b) first and free(a) next, it still
crashes at free(b).
If I comment out free() lines, further down the program, first few characters
of one string get dropped when executes a completely unrelated line.
How could I bit more narrow down the problem?
Many thanks in advance.
Kind regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
--- On Fri, 9/19/08, Unga [EMAIL PROTECTED] wrote:
From: Unga [EMAIL PROTECTED]
Subject: Segmentation fault when free
To: freebsd-questions@freebsd.org
Date: Friday, September 19, 2008, 9:17 AM
Hi all
I'm running FreeBSD 7 on i386. I have a C program
compiled with gcc 4.2.1 20070719.
Logically my program is:
char *a;
char *b;
char *c;
while (cond)
{
a = f1(); /* malloc() and send a string */
b = f2(); /* malloc() and send a string */
c = (char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
free(a);
free(b);
}
When it executes free(b), my program exits with
Segmentation fault: 11. The free(a) executes well.
The problem is with free(b). Even swap free(b) first and
free(a) next, it still crashes at free(b).
If I comment out free() lines, further down the program,
first few characters of one string get dropped when executes
a completely unrelated line.
How could I bit more narrow down the problem?
Many thanks in advance.
Kind regards
Unga
im affraid i didnt implement your request correctly but the program below did
not crash my server under root in 60 seconds
#include stdio.h
#include stdlib.h
#include string.h
char *a;
char *b;
char *c;
char *abd = Hi, im a string 1\0;
char *bbd = Hey, im a string 2\0;
char *f1(void){
char *ab;
ab = malloc(strlen (abd));
memcpy(ab, abd, strlen(abd));
printf(f1(): %s\n, ab);
return ab;
}
char *f2(void){
char *bb;
bb = malloc(strlen (bbd));
memcpy(bb, bbd, strlen(bbd));
printf(f1(): %s\n, bb);
return bb;
}
int
main(void)
{
while (1)
{
a = f1(); /* malloc() and send a string */
b = f2(); /* malloc() and send a string */
c = (char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
free(a);
free(b);
}
}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault when free
--- On Sat, 9/20/08, Nash Nipples [EMAIL PROTECTED] wrote:
From: Nash Nipples [EMAIL PROTECTED]
Subject: Re: Segmentation fault when free
To: freebsd-questions@freebsd.org
Date: Saturday, September 20, 2008, 4:14 AM
--- On Fri, 9/19/08, Unga [EMAIL PROTECTED] wrote:
From: Unga [EMAIL PROTECTED]
Subject: Segmentation fault when free
To: freebsd-questions@freebsd.org
Date: Friday, September 19, 2008, 9:17 AM
Hi all
I'm running FreeBSD 7 on i386. I have a C program
compiled with gcc 4.2.1 20070719.
Logically my program is:
char *a;
char *b;
char *c;
while (cond)
{
a = f1(); /* malloc() and send a string */
b = f2(); /* malloc() and send a string */
c = (char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
free(a);
free(b);
}
When it executes free(b), my program exits with
Segmentation fault: 11. The free(a) executes well.
The problem is with free(b). Even swap free(b) first
and
free(a) next, it still crashes at free(b).
If I comment out free() lines, further down the
program,
first few characters of one string get dropped when
executes
a completely unrelated line.
How could I bit more narrow down the problem?
Many thanks in advance.
Kind regards
Unga
im affraid i didnt implement your request correctly but the
program below did not crash my server under root in 60
seconds
#include stdio.h
#include stdlib.h
#include string.h
char *a;
char *b;
char *c;
char *abd = Hi, im a string 1\0;
char *bbd = Hey, im a string 2\0;
char *f1(void){
char *ab;
ab = malloc(strlen (abd));
memcpy(ab, abd, strlen(abd));
printf(f1(): %s\n, ab);
return ab;
}
char *f2(void){
char *bb;
bb = malloc(strlen (bbd));
memcpy(bb, bbd, strlen(bbd));
printf(f1(): %s\n, bb);
return bb;
}
int
main(void)
{
while (1)
{
a = f1(); /* malloc() and send a string */
b = f2(); /* malloc() and send a string */
c = (char *) malloc(strlen(a) + strlen(b) + 1);
c[0] = '\0';
strcat(c, a);
strcat(c, b);
free(a);
free(b);
}
}
Hi thank you very much for your reply and the test case.
That is, in a trivial case like this, free() works well. Hopefully free() works
well in all cases too.
But my main program is 1900 lines, f1() and f2() are in a 2200 lines second
file. The f1() and f2() calls some functions from a 500 lines third file. The
main program call another function, f3(), from 2nd file, pass pointers to two
functions f4(), f5() of main program. The while loop iterate more than one
million times. Its quite a complex situation.
There must be an error somewhere else. I noted free() causes lot of troubles.
It is easy to write complex programs if you just let to leak memory. But in my
case, since the program iterate millions of times, if I let to leak, I'm sure
it will run out of RAM.
So the question is, if you were to encounter this issue, how would you approach
it and find the culprit?
I'm using pretty basic tools to write complex programs. I use Kate to write
programs, Makefiles to compile, use GCC, and use ddd in case of a trouble.
Best regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Segmentation fault Apache-2.2.9
I continue to see varying amounts of chatter in the 'httpd-error.log' file. This is a snipped of what is being written to the file. ** [Wed Sep 03 06:59:31 2008] [notice] Digest: generating secret for digest authentication ... [Wed Sep 03 06:59:31 2008] [notice] Digest: done [Wed Sep 03 06:59:32 2008] [notice] Apache/2.2.9 (FreeBSD) mod_ssl/2.2.9 OpenSSL/0.9.7e-p1 DAV/2 PHP/5.2.6 with Suhosin-Patch configured -- resuming normal operations [Wed Sep 03 08:28:11 2008] [notice] child pid 1039 exit signal Segmentation fault (11) [Wed Sep 03 08:56:01 2008] [notice] child pid 989 exit signal Segmentation fault (11) [Wed Sep 03 09:29:00 2008] [notice] child pid 1692 exit signal Segmentation fault (11) [Wed Sep 03 09:29:31 2008] [notice] child pid 990 exit signal Segmentation fault (11) ** Some days there may be twenty or more 'segmentation fault' messages. How can I debug this to see what is crashing and why? Everything appears to be operating correctly. -- Gerard [EMAIL PROTECTED] All men profess honesty as long as they can. To believe all men honest would be folly. To believe none so is something worse. John Quincy Adams signature.asc Description: PGP signature
Re: Segmentation fault Apache-2.2.9
Gerard wrote: I continue to see varying amounts of chatter in the 'httpd-error.log' file. This is a snipped of what is being written to the file. ** [Wed Sep 03 06:59:31 2008] [notice] Digest: generating secret for digest [authentication ... Wed Sep 03 06:59:31 2008] [notice] Digest: done [Wed Sep 03 06:59:32 2008] [notice] Apache/2.2.9 (FreeBSD) mod_ssl/2.2.9 [OpenSSL/0.9.7e-p1 DAV/2 PHP/5.2.6 with Suhosin-Patch configured -- [resuming normal operations Wed Sep 03 08:28:11 2008] [notice] child pid [1039 exit signal Segmentation fault (11) Wed Sep 03 08:56:01 2008] [[notice] child pid 989 exit signal Segmentation fault (11) Wed Sep 03 [09:29:00 2008] [notice] child pid 1692 exit signal Segmentation fault [(11) Wed Sep 03 09:29:31 2008] [notice] child pid 990 exit signal [Segmentation fault (11) ** Some days there may be twenty or more 'segmentation fault' messages. How can I debug this to see what is crashing and why? Everything appears to be operating correctly. Easiest thing to try quickly as a stab in the dark is to comment out extension=hash.so in your extensions.ini and restart apache. I and others have had trouble with this one. However, when this particular problem surfaced for me Apache wouldn't start at all, so maybe you're seeing something else. This is just a quick rule out a possible, but deeper investigation is probably warranted in your case. If this doesn't make any difference you can crank up the logging levels in both the Apache config and the php.ini both. Instructions are in the commented out sections of the relevant files. Careful here especially with the php.ini as you don't want the output showing to surfers. Sometimes truss can be a potentially helpful utility. The -f switch will allow it to look at child processes as they fork. truss -f -p [The root Apache PID] -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Segmentation fault: _pthread_mutex_init_calloc_cb()
Hi all When my C program executing exit(EX_OK); I get following error message in ddd: Program received signal SIGSEGV, Segmentation fault. 0x28102600 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 I'm running FreeBSD 7.0 on i386. I noted I got this issue after I introduced a code section with strsep. I'm not sure whether there is anything to do with strsep, ddd shows strsep works well. Any idea what is wrong? Many thanks in advance. kind regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
segmentation fault in claws-mail and firefox
Hello, I'm having an odd problem. When logged into a kde or kde4 session both of these programs work with no errors. When logged into icewm both of these have a segmentation fault with no errors. My guess is some required library is not in the path for these gtk programs, yet they work in kde. I wondered if anyone had a more specific notion, or knew what was happening. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xpdf segmentation fault on FreeBSD 7.0 Release
No, I use the default configuration. It used to be OK, and it seems become fault after I upgrade from FB7 RC4 - Release... Anyway, thank you for reply. Cheers, Kemian On 12/03/2008, Oliver Herold [EMAIL PROTECTED] wrote: No, I'm using it without any problems. Maybe you have some strange configuration in /etc/make.conf? Cheers, Oliver Kemian Dang [EMAIL PROTECTED] wrote: Hi, all, I have installed xpdf 3.02 on a FreeBSD 7.0 Release Box without problem, I can use xpdf -h to get the help information, But when ever I just use xpdf or xpdf some.pdf, it will give a segmentation fault and without any other note. Is there any one have met such things and please suggest me how can I solve it? Best wishes, Kemian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Q: How do you shoot a blue elephant? A: With a blue-elephant gun. Q: How do you shoot a pink elephant? A: Twist its trunk until it turns blue, then shoot it with a blue-elephant gun. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xpdf segmentation fault on FreeBSD 7.0 Release
Hi, all, I have installed xpdf 3.02 on a FreeBSD 7.0 Release Box without problem, I can use xpdf -h to get the help information, But when ever I just use xpdf or xpdf some.pdf, it will give a segmentation fault and without any other note. Is there any one have met such things and please suggest me how can I solve it? Best wishes, Kemian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xpdf segmentation fault on FreeBSD 7.0 Release
No, I'm using it without any problems. Maybe you have some strange configuration in /etc/make.conf? Cheers, Oliver Kemian Dang [EMAIL PROTECTED] wrote: Hi, all, I have installed xpdf 3.02 on a FreeBSD 7.0 Release Box without problem, I can use xpdf -h to get the help information, But when ever I just use xpdf or xpdf some.pdf, it will give a segmentation fault and without any other note. Is there any one have met such things and please suggest me how can I solve it? Best wishes, Kemian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Q: How do you shoot a blue elephant? A: With a blue-elephant gun. Q: How do you shoot a pink elephant? A: Twist its trunk until it turns blue, then shoot it with a blue-elephant gun. pgp51xt7U8h2c.pgp Description: PGP signature
Re: PHP5 segmentation fault
Hello Jeffrey, Jeffrey Lehman pisze: Hello everyone, this is my first post to the list as I am a new FreeBSD user as of last week. I've installed 7.0RC1 amd64 architecture on my poweredge 2950. I'm having issues with apache22 and php5. Here is the process I went through to install both. 1. Installed www/apache22 using 'make install clean' with default config options. 2. Installed lang/php5 using 'make install clean' with default config options plus apache support. Apache seems to be working fine w/o php5 but after I install php5, apache will core dump on restart. PHP5 also seg faults when executing /usr/local/bin/php # /usr/local/bin/php Segmentation fault: 11 (core dumped) Try editing /usr/local/etc/php/extenstions.ini and comment some extensions testing which one is at fault. Usually, it helps to change the order in which they appear to fix this issue. Been there, done that. HTH Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PHP5 segmentation fault
Hello everyone, this is my first post to the list as I am a new FreeBSD user as of last week. I've installed 7.0RC1 amd64 architecture on my poweredge 2950. I'm having issues with apache22 and php5. Here is the process I went through to install both. 1. Installed www/apache22 using 'make install clean' with default config options. 2. Installed lang/php5 using 'make install clean' with default config options plus apache support. Apache seems to be working fine w/o php5 but after I install php5, apache will core dump on restart. PHP5 also seg faults when executing /usr/local/bin/php # /usr/local/bin/php Segmentation fault: 11 (core dumped) Any suggestions would be very appreciative. Thanks! -- Jeffrey Lehman http://digitalguy.net GPG Key fingerprint = 3087 CED0 57F7 3BD3 14E7 969B EE14 BADA D619 8CF5 pgpK13fe5D6qh.pgp Description: PGP signature
Re: segmentation fault in sqlite3 on 6.2R amd64
On 10/2/07, Chad Leigh -- Shire. Net LLC [EMAIL PROTECTED] wrote: Hi In installing trac I ran across a segmentation fault in the initenv command. This seems to be the same problem as shown here: http://www.nabble.com/ports-116383%3A-sqlite3-%28from-databases- sqlite3%29-segfault-tf4449251.html#a12694631 Running it in gdb shows Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x50c000 (LWP 100331)] 0x000802f76869 in sqlite3Fts2InitHashTable () from /usr/public/ lib/libsqlite3.so.8 (gdb) backtrace #0 0x000802f76869 in sqlite3Fts2InitHashTable () from /usr/ public/lib/libsqlite3.so.8 #1 0x000802f74f8f in sqlite3Fts2Init () from /usr/public/lib/ libsqlite3.so.8 #2 0x000802f41be5 in openDatabase () from /usr/public/lib/ libsqlite3.so.8 #3 0x000802e0bd91 in pysqlite_connection_init () from /usr/ public/lib/python2.5/site-packages/pysqlite2/_sqlite.so #4 0x0008006ab6fb in PyType_IsSubtype () from /usr/public/lib/ libpython2.5.so.1 #5 0x00080066ec83 in PyObject_Call () from /usr/public/lib/ libpython2.5.so.1 #6 0x000802e09f95 in module_connect () from /usr/public/lib/ python2.5/site-packages/pysqlite2/_sqlite.so #7 0x00080066ec83 in PyObject_Call () from /usr/public/lib/ libpython2.5.so.1 #8 0x0008006dc6da in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #9 0x0008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ libpython2.5.so.1 #10 0x0008006888be in PyFunction_SetClosure () from /usr/public/ lib/libpython2.5.so.1 #11 0x00080066ec83 in PyObject_Call () from /usr/public/lib/ libpython2.5.so.1 #12 0x0008006dc272 in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #13 0x0008006de336 in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #14 0x0008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ libpython2.5.so.1 #15 0x0008006dd9fb in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #16 0x0008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ libpython2.5.so.1 rest snipped I do the simple test command as shown in the nabble.com link above and get basically the same thing # gdb sqlite3 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... (gdb) r comments.db CREATE TABLE comments (page, name, email, url, body); Starting program: /usr/public/bin/sqlite3 comments.db CREATE TABLE comments (page, name, email, url, body); (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x000800698869 in sqlite3Fts2InitHashTable () from /usr/public/ lib/libsqlite3.so.8 (gdb) backtrace #0 0x000800698869 in sqlite3Fts2InitHashTable () from /usr/ public/lib/libsqlite3.so.8 #1 0x000800696f8f in sqlite3Fts2Init () from /usr/public/lib/ libsqlite3.so.8 #2 0x000800663be5 in openDatabase () from /usr/public/lib/ libsqlite3.so.8 #3 0x00403133 in open_db () #4 0x004053b8 in main () (gdb) Anyone else see this same thing or know about this problem? A Google search does not show this mentioned except at the above link. Thanks Chad Do you have the FTS extension installed? If so, remove it and try again. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: segmentation fault in sqlite3 on 6.2R amd64
On Oct 2, 2007, at 7:07 AM, Maxim Khitrov wrote: On 10/2/07, Chad Leigh -- Shire. Net LLC [EMAIL PROTECTED] wrote: Hi In installing trac I ran across a segmentation fault in the initenv command. This seems to be the same problem as shown here: http://www.nabble.com/ports-116383%3A-sqlite3-%28from-databases- sqlite3%29-segfault-tf4449251.html#a12694631 Running it in gdb shows Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x50c000 (LWP 100331)] 0x000802f76869 in sqlite3Fts2InitHashTable () from /usr/public/ lib/libsqlite3.so.8 (gdb) backtrace #0 0x000802f76869 in sqlite3Fts2InitHashTable () from /usr/ public/lib/libsqlite3.so.8 snipped Do you have the FTS extension installed? If so, remove it and try again. - Max Ok, that fixed the problem but now there is no FTS functionality. That may be ok with the current use, I am checking, but I would like to get to the bottom of this.I am rebuilding sqlite3 with debug to look in gdb. I am not a gdb whiz or anything :-) (doing most of my not often programming on OS X and Cocoa and their debugger frontend to gdb) but will try and see what I can. Thanks! Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
segmentation fault in sqlite3 on 6.2R amd64
Hi In installing trac I ran across a segmentation fault in the initenv command. This seems to be the same problem as shown here: http://www.nabble.com/ports-116383%3A-sqlite3-%28from-databases- sqlite3%29-segfault-tf4449251.html#a12694631 Running it in gdb shows Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x50c000 (LWP 100331)] 0x000802f76869 in sqlite3Fts2InitHashTable () from /usr/public/ lib/libsqlite3.so.8 (gdb) backtrace #0 0x000802f76869 in sqlite3Fts2InitHashTable () from /usr/ public/lib/libsqlite3.so.8 #1 0x000802f74f8f in sqlite3Fts2Init () from /usr/public/lib/ libsqlite3.so.8 #2 0x000802f41be5 in openDatabase () from /usr/public/lib/ libsqlite3.so.8 #3 0x000802e0bd91 in pysqlite_connection_init () from /usr/ public/lib/python2.5/site-packages/pysqlite2/_sqlite.so #4 0x0008006ab6fb in PyType_IsSubtype () from /usr/public/lib/ libpython2.5.so.1 #5 0x00080066ec83 in PyObject_Call () from /usr/public/lib/ libpython2.5.so.1 #6 0x000802e09f95 in module_connect () from /usr/public/lib/ python2.5/site-packages/pysqlite2/_sqlite.so #7 0x00080066ec83 in PyObject_Call () from /usr/public/lib/ libpython2.5.so.1 #8 0x0008006dc6da in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #9 0x0008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ libpython2.5.so.1 #10 0x0008006888be in PyFunction_SetClosure () from /usr/public/ lib/libpython2.5.so.1 #11 0x00080066ec83 in PyObject_Call () from /usr/public/lib/ libpython2.5.so.1 #12 0x0008006dc272 in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #13 0x0008006de336 in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #14 0x0008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ libpython2.5.so.1 #15 0x0008006dd9fb in PyEval_EvalFrameEx () from /usr/public/lib/ libpython2.5.so.1 #16 0x0008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ libpython2.5.so.1 rest snipped I do the simple test command as shown in the nabble.com link above and get basically the same thing # gdb sqlite3 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... (gdb) r comments.db CREATE TABLE comments (page, name, email, url, body); Starting program: /usr/public/bin/sqlite3 comments.db CREATE TABLE comments (page, name, email, url, body); (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x000800698869 in sqlite3Fts2InitHashTable () from /usr/public/ lib/libsqlite3.so.8 (gdb) backtrace #0 0x000800698869 in sqlite3Fts2InitHashTable () from /usr/ public/lib/libsqlite3.so.8 #1 0x000800696f8f in sqlite3Fts2Init () from /usr/public/lib/ libsqlite3.so.8 #2 0x000800663be5 in openDatabase () from /usr/public/lib/ libsqlite3.so.8 #3 0x00403133 in open_db () #4 0x004053b8 in main () (gdb) Anyone else see this same thing or know about this problem? A Google search does not show this mentioned except at the above link. Thanks Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PHP] PHP 5.2.3 - Segmentation fault (core dumped)
Hello, 2007/9/12, Edward Kay [EMAIL PROTECTED]: Dear all, I hope you can help me. I am running FreeBSD 6.2 and I decided to upgrade from php 4.4.7_1 to php5-5.2.3_1. However, after removing php4 and installing php5 and php5-extensions I am unable to start apache. What do the Apache error logs say? Nothing that would be of help: httpd-error.log [Wed Sep 12 09:04:17 2007] [notice] mod_security/1.9.4 configured A new such line is added when I try to start apache. Apache does not start even when I use non-ssl option (apachectl start). messages: Sep 12 12:04:44 szalbot kernel: pid 26602 (httpd), uid 0: exited on signal 11 (core dumped) Many thanks! Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
spumux segmentation fault
Hi everybody! Here is one more problem to solve. Even if I don't put any options for spumux on command line, a segmentation fault is thrown. $ spumux DVDAuthor::spumux, version 0.6.14. Build options: gnugetopt magick iconv freetype fribidi Send bugs to [EMAIL PROTECTED] Segmentation fault (core dumped) $ uname -a FreeBSD xxx.yyy.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Jul 11 06:07:39 PDT 2007 root@:/usr/obj/usr/src/sys/AMD64 amd64 What can I do to fix the problem? Thank you in advance! Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
