On Wed, 4 Dec 2002, Ken Williams wrote:
> Maybe the 'gcc_select 2' command would be a relatively easy way to
> test/debug it? I hadn't known about that command until Paul pointed it
> out.
FYI, last I checked, all that command did was update a symlink so that
(from memory, not on a Mac right now
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Paul McCann) wrote:
> For what it's worth, I had to "sudo gcc_select 3" to get Mac::Carbon to
> compile under 10.2.2. Having changed gcc to "2" in order to get
> curses.pm to work properly I was head-scratching for a couple of minutes
> when Mac:
On Wednesday, December 4, 2002, at 11:41 AM, Chris Nandor wrote:
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Ken Williams) wrote:
Yeah, that looks like exactly what I want. Now if I can just
get Mac::Carbon working under 10.1.5! =) Still haven't had any
luck with that, it looks like
Chris Nandor wrote:
> [EMAIL PROTECTED] (Ken Williams) wrote:
>
> > Yeah, that looks like exactly what I want. Now if I can just
> > get Mac::Carbon working under 10.1.5! =) Still haven't had any
> > luck with that, it looks like a gcc 2/3 issue to me.
>
> Yeah, I dunno. :/ I've not had an
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Ken Williams) wrote:
> Yeah, that looks like exactly what I want. Now if I can just
> get Mac::Carbon working under 10.1.5! =) Still haven't had any
> luck with that, it looks like a gcc 2/3 issue to me.
Yeah, I dunno. :/ I've not had any
On Wednesday, December 4, 2002, at 05:04 AM, Chris Nandor wrote:
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Ken Williams) wrote:
I was thinking about working on Proc::ProcessTable to get
support for OS
X. But after a little effort, it occurred to me that I have
no clue how
to acce
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Jerry Levan) wrote:
> Regrettably sysctl does not give access to table info in the kernel.
Source code and commentary:
http://developer.apple.com/qa/qa2001/qa1123.html
You can get a list of all BSD processes, which includes daemon processes
Well, If we were running linux we could look in /proc.
Possible solutions:
1) Get the source for darwin and study the code for the ps command.
2) Study the header files to find the format for the proc table, examine
the kernel symbol table to get the start address of the proc table. Write
On Tuesday, Dec 3, 2002, at 00:18 US/Pacific, Kris Wolff wrote:
On 03.12.2002 9:09 Uhr, "Ken Williams" <[EMAIL PROTECTED]> wrote:
I was thinking about working on Proc::ProcessTable to get support for
OS
X. But after a little effort, it occurred to me that I have no clue
how
to access process
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Chris Nandor) wrote:
> Mac::Processes can give you much of the information you could want. It
> provides a PSN instead of a PID, but I could add GetProcessPID() and
> GetProcessForPID() to Mac::Processes, which maps between the two. Take a
>
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Ken Williams) wrote:
> I was thinking about working on Proc::ProcessTable to get support for OS
> X. But after a little effort, it occurred to me that I have no clue how
> to access process table information. Anyone know this kind of thing, o
On 03.12.2002 9:09 Uhr, "Ken Williams" <[EMAIL PROTECTED]> wrote:
> Hey,
>
> I was thinking about working on Proc::ProcessTable to get support for OS
> X. But after a little effort, it occurred to me that I have no clue how
> to access process table information. Anyone know this kind of thing,
12 matches
Mail list logo