Re: BSD tar broken file name parsing
File a bug and I'll take a look at it. Bonus if you can check this on -CURRENT; I have fixed a bunch of problems in -CURRENT that aren't yet merged into 6.x but I can't remember right now if this is one of them. Ti Steven Hartland wrote: Just had a really strange one, on a fresh 6.1 install tar will not extract named files e.g. tar -xvzPf my.tar.gz /usr/local/etc/apache/httpd.conf The above fails to extract the file which quite clearly exists: tar -tvzPf my.tar.gz | grep /usr/local/etc/httpd.conf -rw-r--r-- 0 root wheel 37202 May 6 23:30 /usr/local/etc/apache/httpd.conf Similarly -tvzPf naming the file doesnt find the file. Using wild cards finds the file: tar -tvzPf my.tar.gz '*httpd.conf' -rw-r--r-- 0 root wheel 37202 May 6 23:30 /usr/local/etc/apache/httpd.conf I suspect its -P processing that is broken. Installing gtar and using that works fine: gtar -xvzPf my.tar.gz /usr/local/etc/apache/httpd.conf /usr/local/etc/apache/httpd.conf gtar -tvzPf my.tar.gz /usr/local/etc/apache/httpd.conf -rw-r--r-- root/wheel37202 2006-05-06 23:30:58 /usr/local/etc/apache/httpd.conf Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: linux gdb doesnt work at all, fbsd one with problems
Divacky Roman wrote, On 15.7.2006 16:01: > hi > > linux gdb doesnt work at all with internal error (some assert condition doesnt > hold), this is manifested by simple: > > gdb /bin/ls > run > > (sorry cant paste the output now because currently linuxolator panics for me > on every load :)) > > fbsd gdb is not able to attach to a running process: > > witten ~# cat & > [1] 969 > witten ~# gdb > 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 "i386-marcel-freebsd". > (gdb) attach 969 > Attaching to process 969 > /usr/src/gnu/usr.bin/gdb/libgdb/../../../../contrib/gdb/gdb/solib-svr4.c:1443: > internal-error: legacy_fetch_link_map_offsets called without legacy link_map > support enabled. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) > > is there anyone with a GDB fu who can tell me if its gdb's fault, fbsd's fault > or my fault? > > thnx > > roman > > -- > www.liberalnistrana.cz GDB 6.1.1 is pretty ancient. I have had some problems with it dying on certain programmes, too. I didn't get any response on PRs that I filled, so I installed GDB 6.4 by hand and it works fine. So I suggest that, try newest GDB. -- VH signature.asc Description: OpenPGP digital signature
Re: kern/99979: Get Ready for Kernel Module in C++
On Thu, 2006-Jul-13 11:16:18 +0530, Kamal R. Prasad wrote: >Im sorry I didn't understand you. setjmp() stores a few register contents This varies with the CPU - from 48 bytes (i386 and sparc64) to 656 bytes (alpha). In addition, setjmp() stores the signal mask - and accessing this requires a system call - which is comparatively expensive. -- Peter Jeremy pgpE8zWwKy0Fz.pgp Description: PGP signature
Re: fork inside ip_input
In message: <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes: : On 14.07.2006 15:57:28, Simon 'corecode' Schubert wrote: : > Mykola Stryebkov wrote: : > >Hi all. : > > : > >Have a strange question: is it possible to create new process (using : > >fork or fork1) from inside of ip_input()? : > : > i don't think so. : > : > >In kernel sources i found example of using fork1 in init_main.c but : > >looking into ip_input.c i do not understand where i can get pointers to : > >a thread and parent process to pass it into fork1. : > : > only a process can fork, but ip_input is run from interrupt, not in a : > process context. which process do you want to fork anyways? : : I want to start user-level process on first incoming RTP packet to : install and keep TCP control connection. Why not start it at boot, and signal/kick it somehow when RTP connections need to be managed... warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/99979: Get Ready for Kernel Module in C++
In message: <[EMAIL PROTECTED]>
Joerg Sonnenberger <[EMAIL PROTECTED]> writes:
: On Thu, Jul 13, 2006 at 11:16:18AM +0530, Kamal R. Prasad wrote:
: > Im sorry I didn't understand you. setjmp() stores a few register contents
: > [notably ip] in a jmpbuf -which are restored after a longjmp(). How is the
: > try/catch mechanism more efficient than a setjmp()/longjmp() in terms of
: > space/time complexity?
:
: Because you have to run setjmp for *every* try{}, independent of whether
: it is ever actually needed.
It is worse than even that.
You have to run setjmp for every frame, because there could be an
exception thrown from a lower frame to an upper frame and you have to
cleanup your frame when that happens. Variables go out of scope, and
must be destructed, etc.
Warner
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dlsym() on implicit loaded symbols
Roland Dittel wrote: Hi all, We have a issue with dlsym() on symbols imported by a library that was loaded with dlopen(). Our code loads the libssl with dlopen() and then do a dlsym() on several symbols. This works for all symbols exported by libssl itself but fails for symbols exported by libcrypto. Libssl is dynamically linked to libcrypto and should be loaded for libssl. I did a truss and the FreeBSD loader loads libcrypto but does not read anything from the file pointer. could you post a sample code fragment which illustrates the problem you are seeing? cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ signature.asc Description: OpenPGP digital signature
linux gdb doesnt work at all, fbsd one with problems
hi linux gdb doesnt work at all with internal error (some assert condition doesnt hold), this is manifested by simple: gdb /bin/ls run (sorry cant paste the output now because currently linuxolator panics for me on every load :)) fbsd gdb is not able to attach to a running process: witten ~# cat & [1] 969 witten ~# gdb 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 "i386-marcel-freebsd". (gdb) attach 969 Attaching to process 969 /usr/src/gnu/usr.bin/gdb/libgdb/../../../../contrib/gdb/gdb/solib-svr4.c:1443: internal-error: legacy_fetch_link_map_offsets called without legacy link_map support enabled. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) is there anyone with a GDB fu who can tell me if its gdb's fault, fbsd's fault or my fault? thnx roman -- www.liberalnistrana.cz ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
