|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
| LinkBack | Thread Tools | Display Modes |
| |||
How To Get Stack Traces Stack Traces are debugging information you can get from LimeWire that is very helpful in tracking various bugs. If you are reporting a problem with the LimeWire beta series, you may be asked at one point or another to help us by providing such Stack Trace. Here are instructions how to get those: On Windows: 1. Download www.limewire.org/LimeWireDebug.exe and save it in C:\Program Files\LimeWire (or wherever you installed LimeWire) 2. Start LimeWire by opening a dos prompt and typing Code: LimeWireDebug.exe >> stdout.txt 4. Close limewire and send us or post the stdout.txt file. On Mac: 1) Start Console and press the Clear Button* 2) Start Activity Monitor 2.1) select LimeWire from the list 2.2) select "Send Signal to Process" from the View Menu 2.3) select "Quit (SIGQUIT)" from the Menu and press the Send Button 3) Go back to the Console and select "Save a Copy As..."* from the File Menu. *alternatively press the Mark Button, select the output between the marked position and the end, select "Save Selection As..." from the File Menu. On Linux: 1. Start LimeWire by typing "limewire > stdout.txt" in a terminal. 2. Whenever you want to get a stack trace, open another terminal, get the LimeWire process number and issue a kill -QUIT <procNo>. 3. The stack trace will be in the stdout.txt file. We're going to make some changes to make it easier or even automate the above steps, so stay tuned. Last edited by zab; July 24th, 2005 at 12:08 PM. |
| |||
On Mac: 1) Start LimeWire 2) Start Console and press the Clear Button* 3) Start Activity Monitor 3.1) select LimeWire from the list 3.2) select "Send Signal to Process" from the View Menu 3.3) select "Quit (SIGQUIT)" from the Menu and press the Send Button 4) Go back to the Console and select "Save a Copy As..."* from the File Menu. *alternatively press the Mark Button, select the output between the marked position and the end, select "Save Selection As..." from the File Menu. |
| ||||
with terminal on mac: open limewire open terminal then: enter "top" then hit return remember the limewire PID number enter "kill -quit xxxx" where xxxx is the PID number of LW, then hit return Do the same as previous method with the console.
__________________ Liens d'intérêt /Links of interest: Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/ |
| |||
The file should be named LimeWireDebug.exe. If you want to rename it to limewire.exe and overwrite the old one you're welcome to do so, but then you will be stuck running LimeWire with the dos box open until you reinstall. |
| ||||
UH, I need a 101 Windows for Dummies lesson. How do I post results from the DOS window if not by the copy/paste method. My reports are losing something and my DOS window only allows me to go back so far. I use the limewiredebug.exe stdout.txt so if it is going somewheres, where?? |
| |||
If you run "LimeWireDebug.exe stdout.txt" the trace will go in the dos window. That's why you want to run "LimeWireDebug.exe >> stdout.txt" and then the trace will go in a file called "stdout.txt" which you can open with notepad or just upload here. |
| ||||
Hey Zab I am going to join the dummies club. Now if I get the instructions right through this thick scull of mine, with Windows XP Pro I need to start LimeWireDebug.exe >> stdout.txt by going to start/run/command and type in the above is this correct. When I do the above it comes back saying LIMEWIREDEBUG.exe is not recognized as an internal or external command operable program or batch file. So far the only way I have found to run it is to go to go into the LimeWire File and click on the LimeWireDebug icon and the security warning pops up then click on run. Which apparently isn't right, When started the dos window pops up but I cannot enter any text in this window. If I hit Ctrl+Break the report will be written to this window, When it is in this window the only thing I can do is click on the top of the window and right click on it. I then click on properties/select all/copy which apparently isn't right due to lines missing. Please spell it out for a DUMMIES on how to properly use it. Because it isn't doing you guys a damm bit of good for me to be sending you something you cant use. |
| |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to get Stack Traces 4.10.X | Grandpa | LimeWire Beta Archives | 1 | January 21st, 2006 02:26 PM |
4.9.16 Stack Trace | Grandpa | LimeWire Beta Archives | 7 | August 7th, 2005 11:31 PM |
4.9.13 BETA Stack Traces/frozen | deacon72 | LimeWire Beta Archives | 14 | August 4th, 2005 01:17 PM |
Stack Trace don,t know what this is about | Grandpa | LimeWire Beta Archives | 1 | July 29th, 2005 05:14 PM |