* [9fans] tips debugging fs
@ 2006-02-25 16:36 Gabriel Diaz
2006-02-25 18:30 ` Russ Cox
0 siblings, 1 reply; 6+ messages in thread
From: Gabriel Diaz @ 2006-02-25 16:36 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
Hello,
following the example of /sys/lib/lib9p/ramfs.c,
i have done an fs test that dies unexpectedly with
no error message, just " i/o hungup channel " because
the proc died.
i know about memory leaks in there, and i'm trying to
found them with leak, but the proc dies just after running
leak -s.
how can i debug that? i shoud attach acid the first, and then
run leak?
thanks
[-- Attachment #2: Type: text/html, Size: 446 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] tips debugging fs
2006-02-25 16:36 [9fans] tips debugging fs Gabriel Diaz
@ 2006-02-25 18:30 ` Russ Cox
2006-02-25 18:37 ` andrey mirtchovski
2006-02-25 18:53 ` Gabriel Diaz
0 siblings, 2 replies; 6+ messages in thread
From: Russ Cox @ 2006-02-25 18:30 UTC (permalink / raw)
To: 9fans
If the process is not calling exits,
then the broken process should still
be around and debuggable.
ps | grep Broken
and then run acid on that pid.
Running leak on a program should
not change its behavior (it doesn't even
stop the program), so I don't think that's
causing the crash.
Russ
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] tips debugging fs
2006-02-25 18:30 ` Russ Cox
@ 2006-02-25 18:37 ` andrey mirtchovski
2006-02-25 18:53 ` Gabriel Diaz
1 sibling, 0 replies; 6+ messages in thread
From: andrey mirtchovski @ 2006-02-25 18:37 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
> ps | grep Broken
the command 'broke' is also convenient.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] tips debugging fs
2006-02-25 18:30 ` Russ Cox
2006-02-25 18:37 ` andrey mirtchovski
@ 2006-02-25 18:53 ` Gabriel Diaz
2006-02-25 18:56 ` Russ Cox
1 sibling, 1 reply; 6+ messages in thread
From: Gabriel Diaz @ 2006-02-25 18:53 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Hello
i have changed exits() to abort(), but when the error appears,
there is no broken proc, so i suppose is srv.c
who is calling exits :-? but i didn't see any message
(perror should print the message isn't it ? ).
i will add some more prints to see where it die.
thanks
gabi
On 2/25/06, Russ Cox <rsc@swtch.com> wrote:
>
> If the process is not calling exits,
> then the broken process should still
> be around and debuggable.
>
> ps | grep Broken
>
> and then run acid on that pid.
>
> Running leak on a program should
> not change its behavior (it doesn't even
> stop the program), so I don't think that's
> causing the crash.
>
> Russ
>
>
[-- Attachment #2: Type: text/html, Size: 983 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] tips debugging fs
2006-02-25 18:53 ` Gabriel Diaz
@ 2006-02-25 18:56 ` Russ Cox
2006-02-25 19:08 ` Gabriel Diaz
0 siblings, 1 reply; 6+ messages in thread
From: Russ Cox @ 2006-02-25 18:56 UTC (permalink / raw)
To: 9fans
> i will add some more prints to see where it die.
One tip is to run with -D (assuming that does chatty9p++)
and then watch the trace. See which message is causing it
to die.
Another possibility is that you've removed the /srv file
and no one has it mounted, so it is simply exiting normally.
Russ
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] tips debugging fs
2006-02-25 18:56 ` Russ Cox
@ 2006-02-25 19:08 ` Gabriel Diaz
0 siblings, 0 replies; 6+ messages in thread
From: Gabriel Diaz @ 2006-02-25 19:08 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
hello
i just test that and using test -s test -m /mnt/test i can
see a /srv/test, and when the clone fails /srv/test doesn't exist.
it crashed when i finish a read on a file and the last 9p messages are
Read
Tclunk
Rclunk
So I am removing a fid that i need and that is causing fs to exits normally
:-?
gabi
On 2/25/06, Russ Cox <rsc@swtch.com> wrote:
>
> > i will add some more prints to see where it die.
>
> One tip is to run with -D (assuming that does chatty9p++)
> and then watch the trace. See which message is causing it
> to die.
>
> Another possibility is that you've removed the /srv file
> and no one has it mounted, so it is simply exiting normally.
>
> Russ
>
>
[-- Attachment #2: Type: text/html, Size: 1018 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-02-25 19:08 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-02-25 16:36 [9fans] tips debugging fs Gabriel Diaz
2006-02-25 18:30 ` Russ Cox
2006-02-25 18:37 ` andrey mirtchovski
2006-02-25 18:53 ` Gabriel Diaz
2006-02-25 18:56 ` Russ Cox
2006-02-25 19:08 ` Gabriel Diaz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).