[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Tue May 24 08:10:23 2005 -->
- <!--x-from-r13: zcjevtug ng fcrrqsnpgbel.arg ([nex Ievtug) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] C code help -->
- <li><em>date</em>: Tue May 24 08:10:23 2005</li>
- <li><em>from</em>: mpwright at speedfactory.net (Mark Wright)</li>
- <li><em>in-reply-to</em>: <<a href="msg00801.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00796.html">[email protected]</a>> <<a href="msg00800.html">[email protected]</a>> <<a href="msg00801.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] C code help</li>
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
>>> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
>>>
>>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00796" href="msg00796.html">[ale] C code help</a></strong>
<ul><li><em>From:</em> mpwright at speedfactory.net (Mark Wright)</li></ul></li>
<li><strong><a name="00800" href="msg00800.html">[ale] C code help</a></strong>
<ul><li><em>From:</em> greg.freemyer at gmail.com (Greg Freemyer)</li></ul></li>
<li><strong><a name="00801" href="msg00801.html">[ale] C code help</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00833.html">[ale] C code help</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00835.html">[ale] FYI: Inexpensive 802.11g bridge</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00801.html">[ale] C code help</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00833.html">[ale] C code help</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00834"><strong>Date</strong></a></li>
<li><a href="threads.html#00834"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>