Re: Running a program through gdb without "interfering"

2009-10-09 Thread Mel Flynn
On Friday 09 October 2009 21:27:21 Dag-Erling Smørgrav wrote: > Mel Flynn writes: > > Dag-Erling Smørgrav writes: > > > Yes, just run "gdb /path/to/program" and type "run". > > > > Not what I was looking for. The segfaults are random and the only way to > > somewhat reliably reproduce it is to ha

Re: sysinstall colours

2009-10-09 Thread Randi Harper
On Fri, Oct 9, 2009 at 12:52 PM, Alexander Best < alexbes...@math.uni-muenster.de> wrote: > hi there, > > sysinstall is probably one of those ancient relics everybody tries to avoid > dealing with from a developers point of view but i just found this > beautiful > screenie of a (probably) ncurse-b

Re: sysinstall colours

2009-10-09 Thread james toy
Alexander, ==8<== >> http://www.phoronix.net/image.php?id=yoper_2009_beta&image=yoper_dresden_7_lrg ==8<== The head maintainer of Yoper; Tobias G, runs a kernel patchset I work on from http://zen-sources.org as his default kernel. I am sure he would be more than happy to discuss some of their

Re: sysinstall colours

2009-10-09 Thread jhell
On Fri, 9 Oct 2009 21:52 +0200, alexbestms@ wrote: hi there, sysinstall is probably one of those ancient relics everybody tries to avoid dealing with from a developers point of view but i just found this beautiful screenie of a (probably) ncurse-based installer: http://www.phoronix.net/image.p

Re: crashinfo: print the content of ddb capture budder

2009-10-09 Thread Mikolaj Golub
On Fri, 9 Oct 2009 11:28:11 -0400 John Baldwin wrote: JB> On Monday 05 October 2009 1:48:06 am Mikolaj Golub wrote: >> Hi, >> >> It would be nice if crashinfo(8) were also trying to output the content of >> ddb >> capture buffer. Something like in this patch: >> >> --- crashinfo.sh.ori

sysinstall colours

2009-10-09 Thread Alexander Best
hi there, sysinstall is probably one of those ancient relics everybody tries to avoid dealing with from a developers point of view but i just found this beautiful screenie of a (probably) ncurse-based installer: http://www.phoronix.net/image.php?id=yoper_2009_beta&image=yoper_dresden_7_lrg i was

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Dag-Erling Smørgrav
Nate Eldredge writes: > This won't work. You can't debug setuid programs (for reasons which > should be obvious). Ah, true, but easily fixable. Add a sysctl for it (just copy-paste the declaration for kern.sugid_coredump and change the name) and check its value in p_candebug() (hint: "if (crede

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Dag-Erling Smørgrav
Mel Flynn writes: > Dag-Erling Smørgrav writes: > > Yes, just run "gdb /path/to/program" and type "run". > Not what I was looking for. The segfaults are random and the only way to > somewhat reliably reproduce it is to have portmaster invoke it as it's > PM_SU_CMD. And no, running that same com

Re: sigwait - differences between Linux & FreeBSD

2009-10-09 Thread Jilles Tjoelker
On Thu, Oct 08, 2009 at 01:02:09PM +0300, Kostik Belousov wrote: > On Thu, Oct 08, 2009 at 11:53:21AM +1100, Stephen Hocking wrote: > > In my efforts to make the xrdp port more robust under FreeBSD, I have > > discovered that sigwait (kind of an analogue to select(2), but for > > signals rather tha

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Mel Flynn
On Friday 09 October 2009 16:50:04 Mel Flynn wrote: > On Friday 09 October 2009 11:38:29 Dag-Erling Smørgrav wrote: > > Mel Flynn writes: > > > is there a way to have a program run through gdb and gdb only record a > > > segfault, but otherwise let the program run? > > > > Yes, just run "gdb /path

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Nate Eldredge
On Fri, 9 Oct 2009, Mel Flynn wrote: On Friday 09 October 2009 11:38:29 Dag-Erling Smørgrav wrote: Mel Flynn writes: is there a way to have a program run through gdb and gdb only record a segfault, but otherwise let the program run? Yes, just run "gdb /path/to/program" and type "run". Not

newfs -r 2

2009-10-09 Thread Igor Sysoev
I have found that newfs in 8-STABLE has -r switch with zero default value. I think it should be 1 or 2 by default: as I understand, these sectors are not used usually by filesystem anyway since they are not in last cylinder group. Therefore noone would see the difference in usable space, but this r

Re: crashinfo: print the content of ddb capture budder

2009-10-09 Thread John Baldwin
On Monday 05 October 2009 1:48:06 am Mikolaj Golub wrote: > Hi, > > It would be nice if crashinfo(8) were also trying to output the content of ddb > capture buffer. Something like in this patch: > > --- crashinfo.sh.orig 2009-10-05 08:26:26.0 +0300 > +++ crashinfo.sh 2009-10-05 08:43

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Mel Flynn
On Friday 09 October 2009 16:50:04 Mel Flynn wrote: > On Friday 09 October 2009 11:38:29 Dag-Erling Smørgrav wrote: > > Mel Flynn writes: > > > [...] sudo *sometimes* segfaults [...] However, it doesn't dump core > > > > sudo(1) is setuid root. You need to set kern.sugid_coredump to get it > > t

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Mel Flynn
On Friday 09 October 2009 11:38:29 Dag-Erling Smørgrav wrote: > Mel Flynn writes: > > is there a way to have a program run through gdb and gdb only record a > > segfault, but otherwise let the program run? > > Yes, just run "gdb /path/to/program" and type "run". Not what I was looking for. The s

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Stef Walter
Mel Flynn wrote: > [1] In order to get this working I had to put a statically compiled ps in the > jail This is a pretty standard practice. I always put these statically built into any jails that don't match the outside system. I use the following crunchgen config to accomplish that. Cheers, St

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Dag-Erling Smørgrav
Mel Flynn writes: > is there a way to have a program run through gdb and gdb only record a > segfault, but otherwise let the program run? Yes, just run "gdb /path/to/program" and type "run". > [...] sudo *sometimes* segfaults [...] However, it doesn't dump core sudo(1) is setuid root. You nee

Re: Running a program through gdb without "interfering"

2009-10-09 Thread Gary Jennejohn
On Fri, 9 Oct 2009 01:16:59 +0200 Mel Flynn wrote: > On Friday 09 October 2009 00:38:32 Paul B Mahol wrote: > > On 10/9/09, Mel Flynn wrote: > > > Hi, > > > > > > is there a way to have a program run through gdb and gdb only record a > > > segfault, but otherwise let the program run? > > > > > >