This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: run2.exe segfaults when GDI and X11 elements are present

Ken Brown wrote:
> On 12/27/2009 5:31 PM, Ken Brown wrote:
>> I still get a segfault with r23. I'm running XP SP3 if that's relevant.
> I also now get a segfault with the following simpler xml file, which
> I've been using for a long time for starting emacs under X:

This was just a thinko on my part. I forgot to add the following to the
'global node specifies a target' section:

Index: src/run2_main.c
--- src/run2_main.c     (revision 22)
+++ src/run2_main.c     (working copy)
@@ -560,6 +560,7 @@ core_impl (run2_confdata_t *data, s_opts
       run2_env (data, 0);
       startin = run2_get_startin_directory (tgtspec);
       cmd = run2_create_cmdline_from_tgtspec (tgtspec);
+      run2_create_argv_from_tgtspec (tgtspec, &tgt_argc, &tgt_argv);

Fixed in r24. Thanks for the report.

I can't reproduce your segfault with r23/r24 and the original dual xml
file. I'm using Vista...I'll test on XP later today. Can you build with
debugging symbols, run under gdb, and generate a backtrace?

"./libtool --mode=execute gdb --args src/run2.exe --debug=4

(I'm using a self-built gdb; I'm not sure stock gdb supports the
"--args" option. If it does not, then:

"./libtool --mode=execute gdb src/run2.exe"

and you have to do this after gdb starts up:

set args --debug=4 /path/to/test.xml


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]