<div dir="auto">I'm sorry I forgot to get back. I'm not entirely sure what I was doing wrong before but after a rewrite I'm now doing it correctly. I think it had to do with me making assumptions about the state of allocated memory. Thank you for checking up though!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 5, 2019, 4:30 PM Jan Schaumann <<a href="mailto:jschauma@stevens.edu">jschauma@stevens.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jan Schaumann <<a href="mailto:jschauma@stevens.edu" target="_blank" rel="noreferrer">jschauma@stevens.edu</a>> wrote:<br>
> Elliot Wasem <<a href="mailto:ewasem@stevens.edu" target="_blank" rel="noreferrer">ewasem@stevens.edu</a>> wrote:<br>
> <br>
> > What's happening is that when I call<br>
> > fts_children(my_FTS_ptr, 0) after calling<br>
> > fts_read(my_FTS_ptr), it's segfaulting. If I print<br>
> > strerror(errno) right before calling<br>
> > fts_children(...), it says that it failed to<br>
> > allocate memory. When I run $gdb ./ls ./ls.core, it<br>
> > just says there's an error at ?? (literally prints<br>
> > ??) at libc.so.12.<br>
> <br>
> Your libc was not built with debugging symbols, so the<br>
> debugger can't tell you much about that particular<br>
> place in the library. However, it should be able to<br>
> tell you where in _your_ program the execution<br>
> triggered the segfault.<br>
<br>
Did you ever sort out what your problem was?<br>
<br>
-Jan<br>
_______________________________________________<br>
cs631apue mailing list<br>
<a href="mailto:cs631apue@lists.stevens.edu" target="_blank" rel="noreferrer">cs631apue@lists.stevens.edu</a><br>
<a href="https://lists.stevens.edu/mailman/listinfo/cs631apue" rel="noreferrer noreferrer" target="_blank">https://lists.stevens.edu/mailman/listinfo/cs631apue</a><br>
</blockquote></div>