Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-08-01 Thread Michael Enright
On Sat, Aug 1, 2015 at 1:28 PM, Brian Inglis wrote: > > Seems like the problem may be developer confusion between strftime and > printf conversion flag prefixes. The strftime space conversion flag > character is _ so space filled seconds should use %_S, whereas the printf > conversion flag charact

Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-08-01 Thread Brian Inglis
Michael Enright kmcardiff.com> writes: > On Fri, Jul 31, 2015 at 11:46 AM, Michael Enright wrote: > > On Fri, Jul 31, 2015 at 5:51 AM, Jon TURNEY wrote: > The program in question is passing strings to printf that (a) end with > "% " or (b) in the middle have "% S". To be clear these strings are >

Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-07-31 Thread Michael Enright
On Fri, Jul 31, 2015 at 11:46 AM, Michael Enright wrote: > On Fri, Jul 31, 2015 at 5:51 AM, Jon TURNEY wrote: >> >> I think you need to use the gdb command 'set cygwin-exceptions on' to tell >> gdb to break on exceptions <...> > > This is going to help, I have another application (which I don't eve

Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-07-31 Thread Michael Enright
On Fri, Jul 31, 2015 at 5:51 AM, Jon TURNEY wrote: > > I think you need to use the gdb command 'set cygwin-exceptions on' to tell > gdb to break on exceptions inside the cygwin DLL (by default they are > ignored, as they may be generated during normal operation when checking a > pointer is valid) >

Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-07-31 Thread Jon TURNEY
On 30/07/2015 15:39, Jon TURNEY wrote: On 30/07/2015 00:16, Michael Enright wrote: 1) Why is it not the case that gdb handles this SEGV in the usual manner? It too just allows the stackdump to be made and lets me know that the inferior has run its course. This shouldn't happen. Are you sure t

Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-07-30 Thread Michael Enright
On Thu, Jul 30, 2015 at 10:46 AM, Michael Enright wrote: > On Thu, Jul 30, 2015 at 7:39 AM, Jon TURNEY wrote: >> You need to install the 'cygwin-debuginfo' package for debug symbols for >> cygwin1.dll > > I missed this in my searches. I see now that I should have used the > "debug" category. > >>

Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-07-30 Thread Michael Enright
On Thu, Jul 30, 2015 at 7:39 AM, Jon TURNEY wrote: > You need to install the 'cygwin-debuginfo' package for debug symbols for > cygwin1.dll I missed this in my searches. I see now that I should have used the "debug" category. > > You also need to point addr2line at those detached debug symbols,

Re: Analyzing a SEG FAULT that gdb doesn't help with

2015-07-30 Thread Jon TURNEY
On 30/07/2015 00:16, Michael Enright wrote: So I tried to addr2line /usr/bin/cygwin1.dll 6155d363 and I got nothing (?? at ??:?) I then reviewed in setup-x86 the possible cygwin packages to see if there was a missing package I could use to enable cygwin1.dll's addresses to be translated but I did

Analyzing a SEG FAULT that gdb doesn't help with

2015-07-29 Thread Michael Enright
've got a program which was running but suddenly does not run. I've been trying to debug in the usual way but all I get is a stackdump. I consulted the internet for advice on how to use a stackdump and it was pretty clear. I also brought LDD into the mix. The IP register when the SEGV occurs is