On Sat, 9 Feb 2002 "."@babolo.ru wrote:
> Vladislav V. Anikiev writes:
> > The MAC address - I meen The Media Access Control address (i.e., ethernet
> > hardware address, not IP address). I want to use the default hardware (not
> > current physical ) address in my license management software.
I found it interesting. I have 3 idle boxes out here and
friend of mine has ~20, and parallel make is a dream.
Don't know about someone else, I'm giving your proposal
a try.. :-)
On Mon, 21 Jan 2002, Poul-Henning Kamp wrote:
>
> /usr/bin/make already have hooks for remote execution of jobs wh
Hi, folks.
When I switch to DDB to check something or debug something
usefull, mp3 player process (mpg123) hangs up and dissonate
me. So guys how do you do in such a case? I'm shure that
I'm not one having such a problem. ;-)
Maybe someone has allready ported mp3's player to kernel,
or even buil
Hi,
I agree with Serger Babkin - strings(1) wouldn't help.
Main keywords are: ndis.vxd , vip.386 , vtcp.386 .
Any DLL's has nothing common with TCP/IP stack - at least on md 9x.
Sergey Babkin wrote:
> I know one way but it's a hard one: disassemble and manually decomiple
> the code and com
Hello, guys.
Jiangui Liu told right thing - next code fragment
creates a SIGKILL immune allproc entry:
--begin--
#include
#include
#include
#include
int main() {
ptrace(PT_TRACE_ME, 0, 0, 0);
puts(
Hope your program not named "./test" ??
I changed it to /bin/sh and it works just fine.
It was hard to debug due to my own proggie bug :)
bb.
#include
#include
#include
int main()
{
pid_t pid;
if(!(pid=fork())) {
/* child */
eird. Any clue?
>
> ----- Original Message -
> From: "diman" <[EMAIL PROTECTED]>
> To: "Jiangyi Liu" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, May 30, 2001 8:54 PM
> Subject: Re: Weird PT_DETACH
>
>
>
To attach debugger to a process please use PT_ATTACH
request instead of PT_DETACH. Use PT_DETACH to stop
debugging a process and leave it alone.
On 30 May 2001, Jiangyi Liu wrote:
> Hi all,
>
> The ptrace(2) man page is probably outdated. I used PT_DETACH in the
> fol
Core Team, TrustedBSD Project
> [EMAIL PROTECTED] NAI Labs, Safeport Network Services
>
> On Mon, 23 Apr 2001, diman wrote:
>
> >
> > Hello, guys
> >
> > I'm porting ltrace to FreeBSD and have one little question.
> > ltrace uses non-stand
Hello, guys
I'm porting ltrace to FreeBSD and have one little question.
ltrace uses non-standard PTRACE_SYSCALL request, which tells
the kernel to stop traced process on every syscall entry
and notify the parent.
It makes us possible to trace child's syscalls and *catch
execve/xfork events* and
ex.S
#include
.globl main
main: popl%eax/* cick ret */
popl%eax/* cick argc */
movl(%esp),%eax /* eax=av */
movl$fname, %ebx/* ebx=fname */
movl%ebx,(%eax)
Hello, I found a bit more ecsotic way to do this:
- put your fdd to a piece of paper
to make it roll a bit slower
- mount floppy and initiate some
write operation
- regulating the preassure to the device
you can achive the effect
(I/O err., autom. reboot in progress :P)
On Fri, 2 Mar 2
On Thu, 22 Feb 2001, mouss wrote:
> At 18:37 22/02/01 +0200, diman wrote:
>
> >Open AF_UNIX socket to syslogd and then use err_set_file()
> >to redirect all err/warn messages to syslogd instead of
> >stdin/stdout. That should help you debug daemons.
>
> I agr
On Thu, 22 Feb 2001, mouss wrote:
> Now having free() write to stdout/stderr isn't necessarily a good thing
> for daemons. If the message goes through a socket, it'll be hard to
> debug, which was the original intent.
>
> I suggest having some way so that when a program becomes a daemon,
> it
gdb(1) does this definitely. truss(1) gdb for the first and start
thinking.
On Tue, 13 Feb 2001, milunovic wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> Huh thanks those who helped me with some ptrace() examples for Linux.
> But I cann't still figure how to trace programm execution under F
On Fri, 12 Jan 2001, Xavier Galleri wrote:
> OK, let's make it a bit clearer !
...
[skiped]
>
> Now, if you've read my first mail, I was actually asking for help onhow
> to dump the stack of an interrupted process with GDB when the
> kernelcrash occurs in the context of an isr. Actually, I w
On Fri, 12 Jan 2001, Soumen Biswas wrote:
> Hi ,
>
> What are the points to be observed while writing custom init
>
> I am currently doing something like :
> /*
> 1. never exit
>2. open fd 0,1 & 2
>3. link statically */
>
> int main( int argc, char **argv )
> {
> int fd ;
17 matches
Mail list logo
