Hi Rene
Thank you for your suggestions. I was compiling Haiku from Linux and
loading it.
So the modified code is being executed. Confirmation to this is the addon
part which I wrote is being executed.
I'll learn to build Haiku from Haiku today. So that I can just load the
modified library file.
Regards
Hrishikesh
On Tue, May 1, 2018 at 5:31 PM Rene Gollent <anevilyak@xxxxxxxxx> wrote:
On Tue, May 1, 2018 at 6:54 AM Hrishi Hiraskar <hrishihiraskar@xxxxxxxxx>
wrote:
Then you can launch it manually, and receive its stdout:
$ /system/Tracker
I tried this, but the console is still empty. I've `printf ` statementsin tracker code as well as in add on code.
How are you ensuring that your modified libtracker is being loaded? You'd
want to either LD_PRELOAD it, put it in ~/config/non-packaged/lib, or build
a new package with it, otherwise the launched Tracker binary is simply
going to use the existing system libtracker.so, ergo your printfs will not
be executed. You can verify this from Terminal via 'listimage team_id'
where team_id is Tracker's team ID from the process list (i.e. from ps).
Otherwise, the Images tab in Debugger will show you the path of every
executable image loaded in the team's address space. As an addendum, there
is no need to pick a particular thread in Debugger if all you're after is
stdout, the latter is team-wide; you only need to ensure that stdout is
checked in the output capture section at the bottom.
Regards,
Rene
