I started by looking everywhere I thought I called printf in this particular case, and couldn't find a single problematic printf. Given the input I was using, I thought I knew where the printf was probably going to be. But that failed, and there are hundreds throughout the rest of the program. (I use them for generating output and warning/error messages--- I happen to like the format string method of describing your output.)

Then I thought, I sure would like to learn more about the debugger and profiling, so I thought it was worth asking. I never have gotten clear on how to compile libraries for profiling. 

While waiting for a reply here, it struck me where the printf was, and I found it and solved the problem. So there's not an immediate need for the stack trace.

D


On Sat, Dec 5, 2015 at 12:11 AM, Magnus Therning <magnus@therning.org> wrote:

Dennis Raddle writes:

> I'm getting an error, printf not having enough arguments. I need to
> find where this is happening, and I understand there are ways of
> getting a stack trace, but apparently I need to compile for profiling.
> That means I need to compile my one library dependency
> (Text.XML.Light) for profiling, I believe. How do I do this? I'm on
> Windows and have only installed libraries in the past with cabal.

How many calls to `printf` do you actually have?

Wouldn't a search for all calls and a quick inspection of them be good
enough?

/M

--
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus@therning.org   jabber: magnus@therning.org
twitter: magthe               http://therning.org/magnus

If our ideas of intellectual property are wrong, we must change them,
improve them and return them to their original purpose. When
intellectual property rules diminish the supply of new ideas, they
steal from all of us.
     -- Andrew Brown, November 19, 2005, The Guardian

_______________________________________________
Beginners mailing list
Beginners@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners