| To: | Joe Bacom <joebacom@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Seg Fault in libattr |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Thu, 20 Feb 2003 09:10:13 +1100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <200302191419.50007.joebacom@volstate.net> |
| References: | <200302191419.50007.joebacom@volstate.net> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
hi Joe, On Wed, Feb 19, 2003 at 02:19:50PM -0600, Joe Bacom wrote: > Anybody know why libattr.so.1.0.1 would cause a signal 11 segmentation fault > in libncurses.so.5? > > I am building a php extension for accessing extended attributes using the > libattr shared library. When executed, it core dumps with the above seg > fault. Looking at the source for libattr, I can't see a reason for > libncurses to be involved at all. Indeed, libattr does not link with libncurses. What is your actual gdb stacktrace? (and what makes you say that libattr is causing a segfault in libncurses?) cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: been a while before i could get back to this.., Seth Mos |
|---|---|
| Next by Date: | Re: Corrupted file on iso installer image of XFS 1.2, Jason Corbett |
| Previous by Thread: | Seg Fault in libattr, Joe Bacom |
| Next by Thread: | sync doesn't do the job, Jason Li |
| Indexes: | [Date] [Thread] [Top] [All Lists] |