http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From wine(a)transpect.com 2007-01-08 17:42 -------
Okay, these are NOT stripped binaries. From your docs:
"You also need about 400 MB of available disk space for compilation.
The compiled libwine.so binary takes around 5 MB of disk space,
which can be reduced to about 1 MB by stripping ('strip wine').
Stripping is not recommended, however, as you can't submit
proper crash reports with a stripped binary."
Well, I sure didn't invoke 'strip wine'. So if your configure/make routines
didn't strip it, and I didn't, then those are not backtraces from stripped
binaries. However, if you need Wine compiled for some debug level beyond its
default, please specify that and I'll do it.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From the3dfxdude(a)gmail.com 2007-01-08 17:39 -------
I don't know. The default is not to strip them. Something else is wrong. Like
you didn't install the new binaries in there proper places or not calling the
correct wine binary. Check that and I will have you try something in a few minutes.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From wine(a)transpect.com 2007-01-08 17:37 -------
Hey, there's no apparent configure option to not strip the binaries. Is this
something where I have to manually set some variable in the shell first before
building? If so, please specify it.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From wine(a)transpect.com 2007-01-08 17:34 -------
Cool. What's the configure flag to skip stripping the binaries? I'll be happy to
run that again. It's not my choice it's the way it is; it's Wine's default.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From wine(a)transpect.com 2007-01-08 17:32 -------
Jesse,
Please provide instructions for doing either of the things you request. I can
appreciate that if all users were developers, familiar with all the tools, it
would be easier on your end. But we're not. Backtraces I haven't done but a few
times years ago, and regression tests never in this life - despite that I'm a
UNIX sysadmin of 15 years professional experience. I'll betcha I know a lot of
stuff you don't, just like you know these things that I don't. But if you need
me to run them, you'll need to provide the recipe.
Whit
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From the3dfxdude(a)gmail.com 2007-01-08 17:32 -------
Those look like backtraces from stripped binaries. Pretty hard to do anything with.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From wine(a)transpect.com 2007-01-08 17:27 -------
Just to be clearer to Vitaliy, yes InfoSelect is broken on a fresh installation
before ies4lin is installed to it. Please forget I ever mentioned ies4lin. I'm
satisfied (1) it's totally separate, and (2) its being attended to. We're
looking for some other bug freshly introduced to Wine in .42. Hey, it happens.
The point is now to get it back out.
I'm curious, aren't the error messages from Wine that I've attached saying
something to Wine developers? There ought to be something that's obvious in them
to you, even if it's not to me, right?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From the3dfxdude(a)gmail.com 2007-01-08 17:23 -------
Please attach a new backtrace then with debugging symbols, or do a regression
test. Either thing would have helped speed things along in the correct manner in
the first place.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From wine(a)transpect.com 2007-01-08 17:20 -------
Created an attachment (id=7367)
--> (http://bugs.winehq.org/attachment.cgi?id=7367&action=view)
Current git failing to run InfoSelect 1.0
Following Austin's suggestion that this might be a known 16-bit problem since
fixed in git, I've done today's git install, and gotten this failure. A
positive note: the error message list is shorter than in .42. The break is
between .41 and .42. If someone can advise on how to test for it, I do still
have .41 on the system and can compare it with this .42+ git install - but I
don't fully understand the syntax for that git split command.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=9147
------- Additional Comments From wine(a)transpect.com 2007-01-08 17:16 -------
Vitaliy, the has nothing to do with ies4lin - InfoSelect is not a Web-based
application, and in fact predates IE. As for the claim that it's the 16-bit bug,
it's not if that bug is fixed in the cvs as Austin implies. I just did a git
install and it fails similarly. I'll post the attachment of its failure presently.
Trying to "solve" the bug by wishing it to be a duplicate of something is not
productive. At this point I've put a lot of time into verifying the bug, because
it's important it be fixed. You are not contributing anything positive to this
process. Please leave it to others who prefer to solve problems rather than wish
them away.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.