eu-addr2line sez...

0x805fbd3 - urlinstall.c:260
0x804f80b - loader.c:1582

Sorry, that should be urlinstall.c:118, which is the only place strrchr is used in that file anyway.

I think that the problem is that we are treating loaderData->stage2Data coming from iso.boot boot parameters (thus of "hd type" hdInstallData type) as of "url type" urlInstallData. It happens because askmethod + stage2= is broken (bugs #518194 (?), #516973). I sent a patch to fix it for review and the patch should handle also this case (loader goes right to hdd method screen, and after going back and to url method there is the SIGSEGV).
The patch is:
https://www.redhat.com/archives/anaconda-devel-list/2009-August/msg00335.html
If you agree with my analysis, I'm ok with reassigning to me.

*** Bug 519206 has been marked as a duplicate of this bug. ***

I can readily test this 9-5 EST... Let me know if I can help. 

- James

I got the latest boot.iso image dated 9-2-2009 Crash still happens in the some place, but the backtrace is a bit different

loader recieved SIGSEGV! Backtrace:
/sbin/loader[0x804e161]
[0x692400]
/lib/libc.so.6(strrchr+0x3a)[0x9bf9a3]
/sbin/loader[0x805fd08]
/sbin/loader[0x804f7eb]
/lib/libc.so.6(__libc_start_main+0xe6)[0x95cb66]
/sbin/loader[0x804bee1]

Should be fixed in version 12.24 of anaconda. Thanks for the report.

Radek, I am having the same issue this still simply does not work maneuvering as described below. AFAICT I should be using version 12.24-1 of anaconda.

**It should be noted that escaping out of the Install/upgrade screen and specifying 'linux askmethod' at boot: does work and there is not backtrace.**

How to reproduce;

http://mirror.uoregon.edu/fedora/linux/development/x86_64/os/images/

boot.iso	15-Sep-2009 05:36 	167M

After booting from the boot.iso on a usb key and selecting Install/Upgrade, then selecting the language and keyboard, I am presented with the "Select Partition" screen that asks for the "Directory holdings image:" and lists the local sd* devices and prompting to "press F2 to configure additional devices".

After pressing F2 I am presented with the "Driver Disk Source" screen at which point I press Back to finally get to the "Installation Method" screen where I can select URL to install from. After selecting URL it takes you to the "Configure TCP/IP" screen which asks about static or dhcp (either of which produce the same backtrace). 

At this point while configuring NM we receive the following backtrace;

loader recieved SIGSEGV! Backtrace:
/sbin/loader[0x40782e]
/lib/libc.so.6(+0x335f0)[0x7fbd098ee5f0]
/lib/libc.so.6(strrchr+0x1a)[0x7fbd0993dc8a]
/sbin/loader[0x418098]
/sbin/loader[0x408e11]
/lib/libc.so.6(__libc_start_main+0xfd)[0x7fbd098d9b4d]
/sbin/loader[0x4058f9] 
install exited abnormally [1/1]
you may safely reboot your system

As an aside, maybe replacing "you may safely reboot your system" with "Hey, we've had a fatal error here please report to bugzilla.redhat.com" might be more appropriate. 

It appears as if everything works in vty4 and we get an ip get a hostname, but directly after this we see

nm-dispathcer.action: nm_dispatcher_action: Invalid connection: '(null)' /
'connection setting not found' invalid:1  
NetworkManager:    ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-eth0

Again, This boot.iso does work when escaping out of the Install/Update splash screen where you are presented with the 'boot:' prompt and you initiate installation using 'linux askmethod'

James, you should file new bug for your issue, this one is regarding askmethod which, as you said, is working for you. I'll look into your issue.

Radek, Much appreciated. I have reopened my original BZ 519206 and updated it with my last as well. Thanks!

- James

Closing based on the last paragraph of comment #10.