So many great changes, especially glad to see the resume button functional and the automatic bug reporting--congrats to all.

Does the new bug report preference send crashes?

(I'm getting Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000038
pretty regularly, both as an ultrapeer or leaf. OS 10.2.6 running 3.4.2jum196).

Cheers

btw--could the config info generated by the internal error also be made available anytime through the "About LimeWire" screen or "Help" menu? This would be handy so posters could supply this info for troubleshooting in the forums too.

This kind of crash does not send any bug infos to LimeWire. This crash is from the java virtual machine itself crashing, and LimeWire can not do anything about it. Only Apple can fix bugs in the JVM itself.

Most of the info that is generated by a bug report is only interesting in the context of a stack backtrace, so I would believe most would not make sense in a plain vanilla bug report without a backtrace.

Hi jum

Hmm--I thought something was different with this bug since it happened about every hour with jum196, and I'd only seen it about once every two days with the last jum's I was using (jum184) a few weeks ago.

Re the config info (version, IP being used, connection speed, OS, # of files shared, UP status etc), I found it a very convenient way to record what the session config was at the time of an error. I sometimes forget which ISP and settings I'm using, and wanted to record session configuration for my records.

Thanks again for your help and making your builds available. Cheers

PS I just got back this weekend, but am almost finished getting the pics ready for you. I'll email you when I'm done.

Just FYI, the version Jens-Uwe has labelled as 3.4.2 is nowhere near what is actually released as 3.4.2 (well, the actual release is 3.4.3, but same difference). His release is off the current mainline, which has many changes, some of which are relatively unstable.

That said, the easiest way for you to get the kind of information you're looking for is to go to Preferences -> Bug Reports, and click 'View Example'. I'm not sure if we'll put a general 'get my info' button, because as Jens said, it's generally only useful to us in the context of a bug.

Thanks.

Ah! The sample "listing session information"" is close to what I need! Thanks Sam. Nice feature.

btw--the sample "listing session information" shows info from my last session (the IP is from my previous one). Is the example supposed to update whenever the button is used?

Yes, thats what I say in the readme that comes with the build so it should not be a surprise to the user.

BTW, I also do merge bugfix branches into the mainline.

>Yes, thats what I say in the readme that comes with the build so it should not be a surprise to the user.

Great. It's very good to have the releases out there, so people who aren't familiar with CVS and all that can help us test the most recent code. We've found and fixed a few bugs that way.

>the sample "listing session information" shows info from my last session (the IP is from my previous one). Is the example supposed to update whenever the button is used?

It's created whenever the button is pressed. If the IP is from your last session, then you probably haven't connected yet to have someone else tell you what your most recent IP is.

Sam, in order for the IP info to update properly I had to restart the Mac (started LW but didn't connect).

I don't have to restart to switch between the two ISP's I'd been comparing for gnutella connectivity: just change the ethernet cable and the System->Location settings (I do quit LW while switching).

I just tested this again: switched to the 2nd ISP, connected, (incoming and outgoing searches, uploads and downloads show), but the sample button reports the IP from the previous ISP session.

btw, my Pro Beta page shows v3.4.1--don't see a 3.4.3--and have always known the CVS jum builds are "bleeding edge." The install process is so much easier

Hmmm -- which specific line in the info are you saying lists your IP?

FORCED_IP_ADDRESS_STRING

(just sent an internal error, and it now correctly shows FORCED_IP_ADDRESS_STRING).

I think the one I sent in Saturday showed the wrong IP