public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin-xfree@cygwin.com
Subject: Re: possible bug in libXt or libXaw
Date: Sun, 16 Nov 2014 09:14:00 -0000 [thread overview]
Message-ID: <loom.20141116T100601-163@post.gmane.org> (raw)
In-Reply-To: <54684F51.5060706@gmail.com>
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.
One has to reverse the bytes, so it's "b_ncar_c", but that's likely still
not meaningful :-(. You might try:
(gdb) set print pretty
(gdb) p form->form
or
(gdb) p *form->form
and in the output, look at the struct items before horiz_base to see if one
of them is a char array that has been overrun. If it's really hosed, all of
the items may have character string contents which means something before
(lower than) the address of form->form has been overrun.
Good Luck,
..mark
--
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/
next prev parent reply other threads:[~2014-11-16 9:14 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 [this message]
2014-11-16 16:17 ` Marco Atzeri
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=loom.20141116T100601-163@post.gmane.org \
--to=mark@maxrnd.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: link
Be 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).