[ale] C code help

[Mark Wright]

I should probably at least talk to your guy.  I don't have the 
authority to hire anyone but if he could make short work of this issue 
my boss might see the wisdom in paying him to do it.

Can you email me contact info?

Mark Wright
mpwright at speedfactroy.net


On May 23, 2005, at 11:27 AM, Christopher Fowler wrote:

> Good point.  If you do not have the C source then your SOL.  I do have 
> a
> guy that works for me that can work for you to solve this problem.
>
> On Mon, 2005-05-23 at 11:14, Greg Freemyer wrote:
>> Good Luck, that is quite a project.
>>
>> 2 things:
>>
>> 1) If this were Linux code, you could run strace on the code and see
>> all the kernel API calls,  that would pretty much give you the info
>> you are interested in.  Unfortunately, you don't seem to be talking
>> about Linux code here, so I have no ideas.
>>
>> 2) You said you decompiled 2 files.  Decompiled is going to have a
>> specific meaning to a programmer and to the best of my knowledge,
>> there are no tools for decompiling C code.  I have to a assume you
>> meant you reverse engineered a  couple of config files.
>>
>> If you truly meant you decompiled a couple of executable or library
>> files, I'd be interested to know how to do that efficiently.  (I did
>> it once over 20 years ago by dis-assembilng a bunch of .o files into
>> assembly code, then guessing at the original C code, then compiling,
>> comparing, modifying C code, recombiling, recomparing.  It took a long
>> (and tedious) time to manually reverse compile just a couple of .o
>> files.)
>>
>> Greg
>>
>> On 5/22/05, Mark Wright <mpwright at speedfactory.net> wrote:
>>>
>>> Hi Folks,
>>>
>>> I don't really know where to start.  The background to my dilemma is
>>> important but has little to do with the problem.  Suffice it to say
>>> that I am not a coder or very experienced writing scripts but I have 
>>> a
>>> disk image that boots a control device that I need to reverse 
>>> engineer.
>>>
>>> The ultimate end would be to replace the code with our own but for 
>>> now
>>> just getting diag info from it and understanding it would a great 
>>> step
>>> forward.
>>>
>>> I have copied the disk to my Powerbooks hard drive and decompiled two
>>> files  that looked important.  Anybody on the list read c well enough
>>> to read these and tell me what I should do next?  As I said above I
>>> need to understand how it logs events and decode its error reporting.
>>>
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>>
>>> P.S    a little of the background.
>>>
>>> The short story is I work for a very small company.  We have a guy 
>>> who
>>> can probably do this but I know he will never have the time.  The
>>> future of my job may hinge on  knowing the secrets of this device.
>>> Like others have commented on their own jobs, I have tons of spare
>>> time.  I can't sit by and watch my reason for having a job slip away.
>>> I need to become a uber coder in a hurry or find enough help to get
>>> past this to the next issue down the road.
>>>
>>> _______________________________________________
>>> Ale mailing list
>>> Ale at ale.org
>>> http://www.ale.org/mailman/listinfo/ale
>>>
>>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>