[prev in list] [next in list] [prev in thread] [next in thread] 

List:       klik-devel
Subject:    Re: [klik-devel] strace question
From:       "Ng, Cheon-woei" <cheon-woei.ng () intel ! com>
Date:       2008-01-12 0:37:57
Message-ID: F8A0EBD0F30CA24B974BD57423860EAE04CE9BB0 () orsmsx415 ! amr ! corp ! intel ! com
[Download RAW message or body]

Hi Kurt,

Thank you.  I am not sure if this if what I am looking for.  I want to
understand how klik works in the source code level, like 

Klik path_to_cmg would call klik.execute_cmg
Klik.execute_cmg would in turn calls klikExecute(self), then ex.execute
Ex.execute would calls self.__prep
__prep would call self.mount_cmg
So on and so forth.

Other than reading the source code line by line, is there any good/more
efficient way (other than using strace) to understand code path?  

Thanks again! Have a great weekend!

Sincerely,
Woei



-----Original Message-----
From: Kurt Pfeifle [mailto:k1pfeifle@gmx.net] 
Sent: Friday, January 11, 2008 4:17 PM
To: Ng, Cheon-woei
Cc: klik-devel@kde.org
Subject: Re: [klik-devel] strace question

Ng, Cheon-woei wrote:
> Hi Kurt,
> 
> Thanks.  
> 
> The SVN version is 805.  
> 
> Running "klik shell /home/woei/Desktop/xvier_1.0-7.3.cmg" only give
this
> output:  Command is xvier
> 
> Is this an expected behavior? 

Yes.

> What could I do with the output?

You'll be in the root of the fuseiso mount, and you'll have your shell.
You can explore that shell... compare it to a shell running in a
"normal"
terminal ... see what is mounted... try if you can access the
mountpoints
... compare file hierarchies ... find the recipe.xml ... start two
diffe-
rent "klik shell" commands ... compare, explore, find out.

Be curious! :-)

Cheers,
Kurt

-- 
Kurt Pfeifle
System & Network Printing Consultant ---- Linux/Unix/Windows/Samba/CUPS

_______________________________________________
klik-devel mailing list
klik-devel@kde.org
https://mail.kde.org/mailman/listinfo/klik-devel
[prev in list] [next in list] [prev in thread] [next in thread]