From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How about using static link instead of dynamic loaded dlls?
Date: 05 Jun 2003 22:26:15 +0100 [thread overview]
Message-ID: <u7k80w70o.fsf@jasonrumney.net> (raw)
In-Reply-To: <20030605213617.855E.LEKTU@terra.es>
Juanma Barranquero <lektu@terra.es> writes:
> On Thu, 05 Jun 2003 13:06:02 +0100, Robin Hu and Jason Rumney wrote:
>
> > > While compiling with msvc with optimization turned on, Emacs will
> > > emit an access vilation exception while load a tiff file or a png
> > > file. I believe the problem is something related to lookup_image(),
> > > but debug an optimized program is really hard. ;-(
>
> Don't worry: with MSVC 7.0 it happens in non-optimized builds too. I'm
> going to test with 7.1 (aka Visual C++ .NET 2003)
>
> > Why is it hard? You should be able to get at least some idea of where it
> > is going wrong my single stepping through lookup_image. Maybe some of
> > the underlying machine instructions are not what you would expect from
> > looking at the current line, but that should not stop you from getting a
> > general idea of what is happening.
>
> We've already discussed this: you can step till png_load, and then bang!
> The crash happens inside the DLL, and the data being passed to the call
> seems correct... :(
So get the debug symbols for the DLL. One of the tarballs at
probably gnuwin32.sourceforge.net has them, or you can try compiling
it yourself with mingw32 to see if you can duplicate the crash.
next prev parent reply other threads:[~2003-06-05 21:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 3:21 How about using static link instead of dynamic loaded dlls? Robin Hu
2003-06-05 6:53 ` Jason Rumney
2003-06-05 9:05 ` Mike Woolley
2003-06-05 9:51 ` Jason Rumney
2003-06-05 12:28 ` Benjamin Riefenstahl
2003-06-05 10:57 ` Robin Hu
2003-06-05 12:06 ` Jason Rumney
2003-06-05 19:38 ` Juanma Barranquero
2003-06-05 21:26 ` Jason Rumney [this message]
2003-06-05 21:29 ` Juanma Barranquero
2003-06-05 21:52 ` Juanma Barranquero
2003-06-05 17:11 ` David Masterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u7k80w70o.fsf@jasonrumney.net \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).