open All Channels
seplocked Issues, Workarounds & Localization
blankseplocked Easter Eggs: What I found when running 'Strings' Eve Client Binary
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Sel'Na Rey
Posted - 2010.09.29 07:30:00 - [1]
 

So if you get Process Explorer from Sysinternals and check the properties of the ExeFile.exe (which is the Eve Client) then check the Strings tab you'll get a listing of all the ASCII conversion of the binaries bytes. This can show you what sort of messages are in the binary and it can be interesting to see what messages are in some programs you might run. Here is what I found in the Eve Clients that were interesting. I would like to hear from a CCP dev what its point is in the source code or the history behind it.

1) "/jessica" and "/jessica=%d" - I know a %d is a conversion character for printing integers, but this looks like a executable run option. Whats it used for and whose jessica Razz

2) "Do you want to take a look at this?" - Okay CCP no I really don't want to look at 6 month facial growth between expansions, nor do I want to see the inside of your desk draws. Who knows whats been lurking there for the past 7 years.

3) "I had a minor issue :/" - Really now?! Do tell. How does your minor issue make you feel? Does it keep you up at night like it does me?

Okay pretty much the rest of the conversion is mostly gibberish and non human readable, but I am really curious to know what these 3 are.

Glyken Touchon
Gallente
Independent Alchemists
Posted - 2010.09.29 10:39:00 - [2]
 

"Jessica" is an internal tools program at CCP. Would be interesting to know the naming origin thoughVery Happy

Dev Blog

Elysarian
Minmatar
Elysarian Corp
Posted - 2010.09.29 19:02:00 - [3]
 

The other two are possibly comment lines from the source code that weren't removed before it was compiled?

Xentara Vispari
Posted - 2010.09.30 23:23:00 - [4]
 

Originally by: Elysarian
The other two are possibly comment lines from the source code that weren't removed before it was compiled?


Compilers automatically ignore all kinds of comments. It would be a p.i.t.a to remove all comments each time before compiling.

If a string is in the binary, it must be used somehow. But it may be in code path that is only used in special cases (debug, special command line etc.).

Sel'Na Rey
Posted - 2010.10.01 20:30:00 - [5]
 

Originally by: Xentara Vispari
Originally by: Elysarian
The other two are possibly comment lines from the source code that weren't removed before it was compiled?


Compilers automatically ignore all kinds of comments. It would be a p.i.t.a to remove all comments each time before compiling.

If a string is in the binary, it must be used somehow. But it may be in code path that is only used in special cases (debug, special command line etc.).


Xentara is right about compilation stripping comments. So the 2 and 3 items on the list could be part of a string constant used as part of some output. That output might be a dialog, error message, debug message, filename, etc. I highly doubt they would be used in a string comparison, or other control flow statement. My hunch is a debug statement. I'm curious as to what would trigger it Razz

As a side note its a good thing comments are stripped from binaries. Quite a few trade secrets lay in code comments, broken code fragments, failed algorithms, extra debug, and other programmer sanity checks. Binaries in many cases would be 2 - 10x bigger then they are if all comments were left in.



 

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only