public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com> To: cygwin-xfree@cygwin.com Subject: Re: possible bug in libXt or libXaw Date: Sun, 16 Nov 2014 16:17:00 -0000 [thread overview] Message-ID: <5468CE03.50000@gmail.com> (raw) In-Reply-To: <loom.20141116T100601-163@post.gmane.org> On 11/16/2014 10:14 AM, Mark Geisert wrote: > Marco Atzeri writes: >> On 11/16/2014 7:30 AM, Mark Geisert wrote: >>> Marco Atzeri writes: >>>> this is the pointer causing the segfault >>>> >>>> (gdb) p form->form.horiz_base >>>> $2 = (Widget) 0x6275705f6779632f >>>> >>>> while similar pointers have a much smaller address, >>>> >>>> (gdb) p w >>>> $5 = (Widget) 0x60014bd50 >>>> >>>> so it that an assignment not clearing the upper >>>> portion of the pointer. >>> >>> $2 is not a pointer that needed partial clearing, it's a character string >>> "/cyg_pub". Possibly a buffer overrun somewhere? Hope the string fragment >>> points the way to somebody. >>> >>> ..mark >>> >> >> thanks for the hint, "/cyg_pub" is a directory on the root >> >> $ ls -l / |grep pub >> lrwxrwxrwx 1 marco Administrators 19 Jun 26 19:11 pub -> >> /cygdrive/e/cyg_pub >> >> where the data file was stored, >> however moving it to "/tmp" produce as result >> >> p ref >> $1 = (Widget) 0x635f7261636e5f62 aka c_racn_b >> >> that is not very meaningful to me, so the pointer corruption >> can be very generic. I was wrong. It is meaningful (gdb) p form $38 = (FormConstraints) 0x600000003 (gdb) x/20bs 0x600000003 0x600000003: "" 0x600000004: "" 0x600000005: "" 0x600000006: "" 0x600000007: "" 0x600000008: "\023\200" 0x60000000b: "" 0x60000000c: "" 0x60000000d: "" 0x60000000e: "" 0x60000000f: "" 0x600000010: "/tmp/sresa1b_ncar_ccsm3_0_run1_20p/es.nc" 0x600000039: "ht_arrow" 0x600000042: "ow" 0x600000045: "" 0x600000046: "" 0x600000047: "" 0x600000048: "" 0x600000049: "" 0x60000004a: "" So it is a portion of the file name as before, I start to feel that a pointer is not a NULL as should be... > Good Luck, thanks Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2014-11-16 16:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-15 23:30 Marco Atzeri 2014-11-16 6:30 ` Mark Geisert 2014-11-16 7:16 ` Marco Atzeri 2014-11-16 9:14 ` Mark Geisert 2014-11-16 16:17 ` Marco Atzeri [this message]
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5468CE03.50000@gmail.com \ --to=marco.atzeri@gmail.com \ --cc=cygwin-xfree@cygwin.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).