Changing the subject to not hijack the other thread.  Yes, I too have a program 
that basically does a "strings" command on the object code and either dumps all 
strings or for each one looks it up in the VOC to check if it's a file.

-----Original Message-----
[] On Behalf Of Wjhonson
Sent: Wednesday, October 02, 2013 9:46 AM
Subject: Re: [U2] Interesting....

I have to think (and I havent' yet checked) that the names of the files opened 
will appear within the object code, since they have to be represented as 
literal strings when they are named.  Sure you could pass the name in, but then 
the program wouldn't know it either, so we're just talking about files where 
the project itself knows the name of what it's opening.

So you can walk the object code, and reconstruct any literal strings within it. 
 In fact I think I have a tool that does that ....




-----Original Message-----
From: McGowan, Ian <>
To: U2 Users List <>
Sent: Wed, Oct 2, 2013 9:42 am
Subject: Re: [U2] Interesting....

>The use of PORT.STATUS using the "PID" option and "LAYER.STACK" 
> over and over again can show you what hex address in the program your 
> process
is at.  I suggest calling this 
> 50 or 100 times in a row and inspecting the output.  Once you have the 
> hex
addresses, use "VLIST" to figure 
> out what line in the program each address represents.

Does anyone have tips for doing the equivalent in Unidata (when you don't have 
source code, obviously)?  I end up using truss or strace to at least see which 
files are opened/written to, which can be instructive but really hard to follow.
IMPORTANT NOTICE:   This message is intended only for the addressee
and may contain confidential, privileged information.  If you are not the 
intended recipient, you may not use, copy or disclose any information contained 
in the message.  If you have received this message in error, please notify the 
sender by reply e-mail and delete the message.
U2-Users mailing list

U2-Users mailing list
U2-Users mailing list

Reply via email to